http://pike.ida.liu.se/development/pikefarm/result.xml?id=218_163&pike=7... shows yellow blupps in the last couple of builds, but I can't find anything that looks wrong in the verify log. What gives?
If you look at the mainlog, you'll see that it is the benchmark which fails. The benchmark log, in turn, says
/export/d1/xenofarm/pike-7.6/gosroth.roxen.com/buildtmp/Pike-v7.6-snapshot/build/linux-2.6.8-gentoo-r3-ia64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/export/d1/xenofarm/pike-7.6/gosroth.roxen.com/buildtmp/Pike-v7.6-snapshot/build/linux-2.6.8-gentoo-r3-ia64/master.pike -x benchmark Lost track of a child (pid -1, errno from wait 10). _static_modules.Builtin()->create_process: _static_modules.Builtin()->create_process()->wait() /export/d1/xenofarm/pike-7.6/gosroth.roxen.com/buildtmp/Pike-v7.6-snapshot/lib/modules/Tools.pmod/Shoot.pmod/module.pmod:102: Tools.Shoot.ExecTest()->run(0,1,1) /export/d1/xenofarm/pike-7.6/gosroth.roxen.com/buildtmp/Pike-v7.6-snapshot/lib/modules/Tools.pmod/Standalone.pmod/benchmark.pike:65: Tools.Standalone.benchmark()->main(1,({"/export/d1/xenofarm/pike-7.6/gosroth.roxen.com/buildtmp/Pike-v7.6-snapshot/lib/modules/Tools.pmod/Standalone.pmod/benchmark.pike"}))
errno 10 ought to be ECHILD. The manpage for wait says
ERRORS ECHILD (for wait) The calling process does not have any unwaited-for children.
ECHILD (for waitpid) The process specified in pid does not exist or is not a child of the calling process. (This can happen for one's own child if the action for SIGCHLD is set to SIG_IGN. See also the LINUX NOTES section about threads.)
Not all that helpful, perhaps...
Pike starts itself in those tests, so that part is more or less a test of create_process and process->wait...
ExecTest is the benchmark when pike starts itself to quit immediately.
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum -
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Mirar ＠ Pike developers forum