-
-
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
Defect: allocate_as_barrier_proc
test still fails intermittently
#415
Comments
Here is a link to a CI job that I won't rerun, that shows the error: https://travis-ci.org/sourceryinstitute/OpenCoarrays/jobs/262671942#L2947 |
Well, this is difficult to reproduce. On Linux I have no problem when running the test multiple times nor when running it with increasing number of processes 2-64 (more won't work on my machine: overload). |
Yes I agree that this is very difficult to debug. I mostly just want to track it and document it here. Unless some insight can be gained from inspecting the code responsible for implicit synchronization of subroutines that do allocation, we can just sit on this issue---at least until it's observed in the wild. |
This seems to happen more when compiling with clang, or using OpenMPI |
Here is a more helpful debug log, but may not have all of the required information: (See https://travis-ci.org/sourceryinstitute/OpenCoarrays/jobs/373497931#L1733)
|
This appears to be fixed on GFortran >= 7. I'm going to close this after adding having CMake disable this test if( ( NOT CMAKE_Fortran_COMPILER_VERSION VERSION_LESS 7.0.0 ) OR OPENCOARRAYS_DEVELOPER ) Here is the debug output for GCC 6.4:
|
Defect/Bug Report
uname -a
: Good question, I should add this to .travis.yml... dockerized MacOSObserved Behavior
Test
allocate_as_barrier_proc
fails with:(https://travis-ci.org/sourceryinstitute/OpenCoarrays/jobs/253477906#L3460)
Expected Behavior
Test passes
Steps to Reproduce
Run on CI and repeat test a lot with CTest. @afanfa or @vehre if you want me to show you how to do this, please let me know.
The text was updated successfully, but these errors were encountered: