Open pperanich opened 2 years ago
https://github.com/facebookresearch/labgraph/blob/main/test_script.sh can be used for testing instead.
Testing with that scripts works, but running the test suite all together shouldn't cause a memory bus fault as is the case described above. If this is expected behavior, can we document why that is?
Agree, it is possibly because the graph is not shut down completely for the pytest test_hang test case, I'll take a look at this.
🐛 Bug
When running pytest on the whole Labgraph module, via
python -m pytest --pyargs -v labgraph --ignore=labgraph/devices
, the testlabgraph/runner/tests/test_exception.py::test_hang
fails on[ProcessPhase.STOPPING]
every time with a SIGABRT. However, running these tests alone, viapython -m pytest --pyargs -v labgraph.runners.tests.test_exception
, passes.To Reproduce
Steps to reproduce the behavior:
Dockerfile
, e.g.,docker build . -t labgraph
docker run -it labgraph bash
gdb -ex r --args python3.9 -m pytest --pyargs -v labgraph --ignore=labgraph/devices
Since I ran with GDB, I was able to run a backtrace after the SIGABRT (find log file attached below):
It looks like the culprit is
cthulhu::Framework::validate()
which is throwing theSIGABRT
. This can be traced back to: https://github.com/facebookresearch/labgraph/blob/6742cefe72e86c31ba835197808d4d7f397b40d9/Cthulhu/src/FrameworkIPCHybrid.cpp#L125-L130log.txt
Expected behavior
Test suite should not SIGABRT.
Environment
manylinux2014
container)