On Fri, Feb 19, 2010 at 06:08:07PM -0500, Joey Hess wrote:
> If parallel called waitid() with no child to wait for, then it would
> have a bug in its control logic (ie, a fencepost bug) that would probably
> manifest in other ways than the exit code; such as running too many or
> too few parallel processes.
>
> At this point all I have is speculation that parallel is broken, but
> nothing to go on to fix it. I'll need a command line, a test case, a
> strace, or *something*.
I had a strace, but it was rather large since I also straced all
the children. I'll see about making a new strace.
Anyway, we currently call it like:
parallel -l 5 -i trigger_wb_update_arch_loop "${SUITE}" "{}" "${SOURCES}"
"${PACKAGES}" "${WB_SUITE}" -- ${ARCHS}
But I've also done it without the "-l 5".
Kurt
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
