Closed vlandau closed 3 years ago
Thanks for the report. What version of julia? I think there is a chance this is fixed on master or release-1.6.
This was on Julia 1.5.3 -- no problems on 1.6.0-beta1! I figured there might not be another patch release for 1.5, but I wanted to post the issue here just in case there will be.
Wonderful, thanks for checking!
I've encountered a seemingly non-deterministic bug when running tests for Omniscape.jl on GitHub Actions. It is triggered during a test for a function that uses multithreading. The serial implementation of the same function passes reliably. The only difference between the two versions of the function is that one uses a for loop, and the other uses a
@threads
for loop. Following no additional changes to source code, CI suddenly started failing with this output:At first, the error only occured on Ubuntu, and passed on MacOS, then when rerunning tests (again with no changes to source code) it failed on MacOS but passed on Ubuntu. Now it is failing on both. I'm unable to reproduce locally, but I was able to SSH into the Github Actions runner. The tests seem to fail reliably if tests have already been run at least once. When running package tests from the SSH session, I get this error, though: (but I guess a ReadOnlyMemoryError is a type of segfault?)
I ran the test with --bug-report=rr to upload a bug report, but because the error seems non-deterministic, I can't be positive that the error was triggered because no output was shown in the terminal when running tests with bug reporting enabled. The error happened, though, in tests just before and just after running with --bug-report=rr, so I'm hoping the bug report contains the pertinent information.
Here is a link to the bug report.