-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continuous
tests stuck in arm64
container
#238
Comments
This does not appear to be a problem when testing on |
Hmm, if it is after Cardiac Simulation it probably is unrelated, can you run with just one core so you see which one has launched and got stuck? |
Hmm, they all passed when running with a single core! Perhaps there's a race condition somewhere? |
I've just built a new
|
Continuous
tests stuck after TestCardiacSimulation
in arm64
containerContinuous
tests stuck in arm64
container
Describe the bug
When testing the new
2024.1
release in a docker image, it builds fine and most of theContinuous
tests run fine, but they get stuck just afterTestCardiacSimulation
(needing to be manually stopped after ~1 hour on an M1 Max MBP).To Reproduce
Steps to reproduce the problem.
Expected behavior
The whole
Continuous
test suite should only take a few minutes.System
Please provide relevant details of your system, such as:
PETSc: 3.15.5
Boost: 1.74.0
HDF5: 1.10.7
Parmetis: 4.0.3
XSD: 4.0.0
SUNDIALS: 5.8.0
VTK: 7.1
Xerces: 3.2.3
Please paste the full output in a code block. It will be similar to the truncated example below.
The text was updated successfully, but these errors were encountered: