xulrunner-1.9 build leaves orphaned find processes, hangs buildds
Bug #162723 reported by
James Troup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xulrunner-1.9 (Ubuntu) |
Fix Released
|
High
|
Fabien Tassin |
Bug Description
Binary package hint: xulrunner-1.9
After a build of xulrunner-1.9 on any of our builders, one or more orphaned children are left around, e.g.
buildd 6059 0.0 0.0 1704 560 ? S 18:16 0:00 find mozilla -type f -name *.pyc -exec rm {} ;
buildd 6060 0.0 0.0 1700 544 ? S 18:16 0:00 find mozilla -type l -exec rm {} ;
These orphans are not detected by our builders, so they hold up the buildd and other builds until they're killed by the inactivity check.
Please figure out why these processes are becoming orphaned and stop it from happening. strace after the fact was unintersting, both were stuck in semop()
Related branches
Changed in xulrunner-1.9: | |
importance: | Undecided → High |
To post a comment you must log in.
Heh, actually looking at the log, it's pretty obvious...
find mozilla -type f -name \*.pyc -exec rm {} \; &> /dev/null; \
find mozilla -type l -exec rm {} \; &> /dev/null