2 tests fail: tests.py::test_rumur[True-False-smt-bv-add.m-debug, tests.py::test_rumur[False-True-smt-record-bool-field2.m-XML]

[yurivict]

log

Version: 2025.01.05
Python-3.11
FreeBSD 14.1

[Smattr]

Thanks for reporting.

Is it possible this was resource exhaustion? Three things surprise me:

• These tests passed in pre-merge CI on FreeBSD 14.0.
• The labels like “gw0”, “gw1”, “gw2”, “gw3” suggest to me the test suite is running parallelised. Is this correct? The CMake files deliberately don’t call Pytest multithreaded because of past resource exhaustion problems. Some of the tests themselves are multithreaded, so running multiple test cases concurrently can overwhelm the machine.
• The tests that failed are parameterised ones. The True-False, False-True prefixes relate to multithreading and optimisation. If tests like these fail, I would expect all 4 of the matrix {False, True} × {False, True} to fail.

[yurivict]

The labels like “gw0”, “gw1”, “gw2”, “gw3” suggest to me the test suite is running parallelised. Is this correct?

This is possible. The following PyTest plugin might be enabling parallelism by default:
py311-pytest-xdist-3.6.1,1 Pytest xdist plugin for distributed testing and loop-on-failing modes