Open gitoliver opened 11 months ago
I've now seen this when running tests in the grpc delegator:
Testing 000.buildBySequence.cc... In file included from /programs/gems/gmml/includes/gmml.hpp:164,
from tests/000.buildBySequence.cc:1:
/programs/gems/gmml/includes/Resolver/PdbPreprocessor/pdbpreprocessor.hpp:471:9: internal compiler error: Segmentation fault
471 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
Test FAILED!
buildBySequence.pdb does not exist.
Exit Code: 1
At the same time I saw test 019 failing too:
Testing 019.test.newPDBClass.cpp... ~30 seconds. ./019.test.newPDBClass.sh: line 14: 1582 Segmentation fault (core dumped) ./newPdbClass tests/inputs/"${file}" > 019.output.txt
Test FAILED!. 019.output.txt different from tests/correct_outputs/019.2n7b.pdb-output.txt
Compare using diff
Exit Code: 1
This has been resolved in gmml2 here https://github.com/GLYCAM-Web/gmml2/commit/c4005e8e8922c7f02c18352c88af3693159deb70 As for gmml, well, i absolve myself of responsibility.
This happens on bare metal too, and so far only when running with other tests as a batch. Re-running the test by itself, or in a batch often has everything pass. Given the intermittent behavior, and that it only shows up when running as a batch of tests, I suspect the threading code for bond by distance has a fatal flaw.