Sept 26: 16:57 < philor> did someone touch the creation/logging of screenshots on timeouts recently? 16:59 < philor> scroll up from https://tbpl.mozilla.org/php/getParsedLog.php?id=28435155&full=1&branch=mozilla-inbound#error0 - the screenshot before the timeout is odd, but whatever; the other one above that just ain't right The code from bug 746243 should be audited to see what has changed regarding screenshots and the issue fixed.

This appears due to the lack of piping in the mozprocess call: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#681 we actually do pipe, but the outputhandler writes to stdout, so we should block that from happening. So here we should pass a handler to accumulate the output to supress the default of printing.

So I'm thinking of

(In reply to Jeff Hammel [:jhammel] from comment #4) > So I'm thinking of (beh, form submit too soon) ...of changing this bug to move the dumpScreen function to automationutils.py mostly because its easier to test, but also because I need it for bug 915865 . In this case, I would - get rid of the `self` references, which are only used for ensuring dumping is done but once - ... and keep this functionality in `runtest.py` - use subprocess.Popen instead of mozprocess.ProcessHandler. why? because i'm not 100% sure that mozprocess is available everywhere that automationutils is imported nor does it seem critical for this particular problem. - add a CLI front-end to test this functionality. I'd be willing to include this for checkin or not What do you think, Ted?

the full on -> automationutils.py change; from comment 5

(In reply to Jeff Hammel [:jhammel] from comment #6) > Created attachment 813345 [details] [diff] [review] > bug-921676 > > the full on -> automationutils.py change; from comment 5 green try: https://tbpl.mozilla.org/?tree=Try&rev=4e1e9f794505

data uri using mozprocess; does not work

data uri using subprocess; works

I've been working on the alternate "simple" solution (that is, just putting the pipe in place). However, there is a problem with using mozprocess to save the screenshots aside from that. Could be my mistake, but, could be a mozprocess issue. TBD.

code to get results from comment 8 and comment 9

FWIW, every single OS X screenshot from a 330 seconds without output timeout that I've seen today has had no browser window, no sign we're still running, like it has been taken far too late, after we've already killed the browser.

jhammel: Your plan sounds pretty plausible. philor: that sucks, maybe MozRunner is killing the process before we get around to it?

pushed to try: https://tbpl.mozilla.org/?tree=Try&rev=923906412841 Looks green; will land on inbound

pushed to inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/ef2d30255b7a