enter-github-username
enter-github-username
Running the test suite in parallel via the `-j` flag of make currently leads to test failures. This is likely caused by some tests trying to bind to the same...
Some tests are flaky if they are executed in parallel, i.e. one or more of them may suddenly fail. The affected tests are `test/t-chain`, `test/t-chaindb` and `test/t-wallet`. This issue may...
Automake allows the execution of tests in parallel by adding the -j parameter to make check. However, doing this breaks a large amount of tests (like e.g. `tests/usrdef_ipaddr_dotdot.sh`), as they...
Some tests, like `test/facility.sh`, use hard-coded sleep statements to ensure that prior operations finish. While running the test suite of sysklogd inside a heavily CPU-limited podman container, a few tests...
The two tests `test/t-autocompact` and `test/t-corruption` can fail unexpectedly on low-power systems (like e.g. a CI worker with restricted CPU resources or old hardware), as the hardcoded time of 1...
Several tests are dependent on the output (several *.TEST files) of other tests: `readnestedform` and `searchforms-nestedform` are dependent on `writenestedform` `validcat.sh` and `readcat` are dependent on `writecat` `searchforms-form`, `lookupproperty-simple`, `validform.sh`,...
While running benchmarks on selFIe, I found that the test `selfie_hellovar.sh` is flaky, i.e. it fails sometimes. The test [selfie_hellovar.sh](https://github.com/cea-hpc/selFIe/tree/master/test/selfie_hellovar.sh.in) saves the current timestamp into the SELFIE_TEST variable. After the...
Running the test suite in parallel (using `make -j16 check`) causes tests to randomly fail. The log files of the failing tests contain this error: ``` event.tst: tester.c:79: tester_create: Assertion...