glib/tests/spawn-singlethread often fails /gthread/spawn-script
@dmacks
Submitted by Daniel Macks Link to original bug (#731367)
Description
After building glib-2.38.2 on OS X 10.8, running the test suite sometimes gives:
FAIL: spawn-singlethread
but sometimes does PASS instead. When it fails, spawn-singlethread.log reports:
random seed: R02S32ea9ef61578d2c1cee3a5b235b3a6d0
Start of gthread tests
ok 1 /gthread/spawn-single-sync ok 2 /gthread/spawn-single-async
GLib-FATAL-WARNING: In call to g_spawn_sync(), exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_spawn_sync either directly or indirectly.
(/sw/build.build/glib2-shlibs-2.38.2-1/glib-2.38.2/glib/tests/.libs/spawn-singlethread:7739): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_spawn_sync either directly or indirectly. ../../tap-test: line 5: 7739 Trace/BPT trap: 5 $1 -k --tap
Firing up repeated testing:
while true; do ./spawn-singlethread;done
finds that that third test (/gthread/spawn-script) seems to fail that way about 3/4 of the time, with no obvious pattern. The system is lightly loaded at all times.
Version: 2.38.x