| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Jenkins Console Log Machine information No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal CPU: G++: Clang: |
Sorry, something went wrong.
|
I've also split the tests across more runners, bringing the total runtime down to ~1.5hours. Given that the Jenkins mix unit tests take ~4 hours, maybe we could look at using the github runners for the basic unit tests instead (leaving the GPU, mpi, etc for Jenkins)? That could speed the CI process up a bit and also free up the resources for the CI in the other repos |
Sorry, something went wrong.
|
We could also split up the Jenkins jobs into more parallel executors. Especially if they end up being short-lived, I don't think that would be a problem -- but I'd look into it in a separate PR rather than at the same time as this |
Sorry, something went wrong.
There was a problem hiding this comment.
Two minor comments but this looks good -- thanks!
Sorry, something went wrong.
Jenkins Console Log Machine information No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal CPU: G++: Clang: |
Sorry, something went wrong.
Jenkins Console Log Machine information No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal CPU: G++: Clang: |
Sorry, something went wrong.
|
Hey @andrjohns, I've noticed some extra flakiness in the windows tests after this -- e.g, These passed during the CI of #3151, which was using the old action at the time. Any idea what's up? |
Sorry, something went wrong.
|
Update: Run #4 did pass. Definitely worth looking into more next week |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Now that arm64 runners are available in github actions, we can add them as part of our regular CI. This will help catch issues like those fixed in #3059 - it's already identified issues with owens_t!
The owens_t function was hanging indefinitely under the arm64 runner, and this was resolved by adding our boost_policy definition as an argument - I'm not entirely sure why (might be another precision thing?).
I've added the runners as part of the existing Windows Rtools CI, using pwsh to avoid changing the current workflow in any meaningful way.
Tests
N/A - existing tests should still pass
Side Effects
N/A
Release notes
Add arm64 linux to Github Actions CI
Checklist
Copyright holder: Andrew Johnson
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
the basic tests are passing
the code is written in idiomatic C++ and changes are documented in the doxygen
the new changes are tested