https://tbpl.mozilla.org/php/getParsedLog.php?id=7519304&tree=Mozilla-Inbound talos-r4-snow-037: Started Mon, 21 Nov 2011 17:07:48 Running test dromaeo_css: Started Mon, 21 Nov 2011 17:07:48 Failed dromaeo_css: Stopped Mon, 21 Nov 2011 17:07:48 FAIL: Busted: dromaeo_css FAIL: Found processes still running: firefox. Please close them before running talos. Traceback (most recent call last): File "run_tests.py", line 596, in <module> main() File "run_tests.py", line 593, in main test_file(arg, options.screen, options.amo) File "run_tests.py", line 535, in test_file raise e utils.talosError: 'Found processes still running: firefox. Please close them before running talos.' program finished with exit code 1 elapsedTime=0.490388 https://build.mozilla.org/buildapi/recent/talos-r4-snow-037 says the previous job was a happy green Jetpack and the job before that was a happy green Talos, so only the Talos and the Jetpack could have left something running.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7520230&tree=Mozilla-Inbound n-1 was a red Jetpack run. Just sayin'.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7781249&tree=Mozilla-Beta n-1? That'd be a red Jetpack run.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7781301&tree=Mozilla-Beta n-1? Jetpack.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7781344&tree=Mozilla-Inbound n-1? Why yes.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7773672&tree=Services-Central n-1? Already too far back for me to see.

But now that I've been retaught how to go back, n-1? Jetpack. n-1? Jetpack.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7804585&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=7804578&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=7804590&tree=Mozilla-Inbound

Checking the log for a recent n-1 jetpack run[1], we're not even making it to the point where firefox runs. It looks like we be running into issues with the dmg install process (installdmg.sh). That is probably holding open a process with firefox in the name. I don't know what to do here. The whole point of installdmg.sh was to bulletproof some of the hdiutil pain. Maybe we need more kevlar for rev4 slaves? :/ 1. http://buildbot-master11.build.scl1.mozilla.com:8201/builders/jetpack-mozilla-central-lion-debug/builds/15

https://tbpl.mozilla.org/php/getParsedLog.php?id=8671029&tree=Mozilla-Inbound n-1? peptest, which really should not be running in its current form.

https://tbpl.mozilla.org/php/getParsedLog.php?id=8670915&tree=Try - a timeout that killed some process, but apparently not the firefox process.

But in the jetpack case (which I'm hitting a whole lot tonight, because we landed a patch that makes them die on startup), isn't the problem that we don't reboot at the end of the run, like we do with every other sort of test including on-push jetpack, but not jetpack-tree-jetpack?

Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.