Running "make -j3 -f posix.mak unittest", a FAIL appeared, but make continued checking. Thus this FAIL was gone unseen:
[...]
****** FAIL debug64 std.algorithm.sorting
core.exception.AssertError@std/algorithm/sorting.d(1963): You seem to have improved sort! Please update watermark from 1676280 to 1676220
----------------
??:? onAssertErrorMsg [0x7fb0d2d16d97]
??:? onUnittestErrorMsg [0x7fb0d2d16e19]
??:? _d_unittest_msg [0x7fb0d2d170a0]
??:? @safe void std.algorithm.sorting.__unittest_L1937_C7() [0x7fb0d2175086]
??:? void std.algorithm.sorting.__modtest() [0x7fb0d2267865]
../druntime/src/test_runner.d:61 [0x55657c873657]
../druntime/src/test_runner.d:32 [0x55657c873563]
../druntime/src/test_runner.d:13 [0x55657c87339b]
??:? runModuleUnitTests [0x7fb0d2d17c44]
??:? void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll() [0x7fb0d2d41109]
??:? void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).tryExec(scope void delegate()) [0x7fb0d2d41084]
??:? _d_run_main2 [0x7fb0d2d40fea]
??:? _d_run_main [0x7fb0d2d40d5a]
../druntime/import/core/internal/entrypoint.d:34 [0x55657c873951]
??:? __libc_start_main [0x7fb0cef1109a]
make[1]: *** [posix.mak:395: unittest/std/algorithm/sorting.run] Fehler 1
make[1]: *** Es wird auf noch nicht beendete Prozesse gewartet....
../dmd/generated/linux/release/64/dmd -conf= -I../druntime/import -w -de -preview=dip1000 -m64 -fPIC -transition=complex -O -release -unittest -c -ofgenerated/linux/release/64/unittest/std/experimental/checkedint.o std/experimental/checkedint.d
[...]
Comment #1 by bugzilla — 2020-03-20T06:35:30Z
Running make with -j3 will use multiple threads. If one thread fails, the others will continue to run. It's how make is designed to run. I suspect this is the cause of the behavior you're seeing. If not, please reopen and clarify.