-
Notifications
You must be signed in to change notification settings - Fork 21
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
ADIOS2 Tests Failing with ADIOS2 2.9.0 #133
Comments
@burlen not sure if you've hit these issues before as well |
Just for reference, this is the output I'm getting when running ADIOS2SST test with ADIOS2 2.9.0 on the testing container.
|
@vicentebolea does this failure look familiar? I know you were porting some ADIOS2 2.9 changes a while back |
@willdunklin not to me, run those tests manually with the env variables set to SstVerbose=100 SstCPVerbose=100 |
At the end of the error message
could it be old file from a previous run is found, that we or adios changed the default time out for sst, or we need to increase the timeout on cloud test system? |
That looks like you are running the SST test in the same dir where that test was run before and it was not cleaned up. |
@vicentebolea Here's that more verbose output from the first of the two tests:
|
running this with GDB will probably tell us the reason of this. |
From my CI work I've noticed that building SENSEI with ADIOS2 2.9.0 causes the following tests to fail:
Both tests seem to be segfaulting with 2.9.0, but work fine with 2.8.3.
Let me know if logs of the errors would be helpful. I also have a docker test image that has ADIOS2 2.9.0 installed if that would help with reproducibility. You can find the docker image here, make sure to mount your SENSEI source to
/sensei/src
in the docker container.The text was updated successfully, but these errors were encountered: