Hey Jonathan, So I've observed something like this when running tests on the emulator.
What exactly is marionette parsing to determine if tests pass or fail? Is it the adb log? or console log? Is there a buffering effect happening and maybe the output is just being delayed in getting delivered? Like maybe some test after the one thats timing out is causing lots of CPU to be consumed and this winds up holding up the log data from being delivered? Dave Hylands ----- Original Message ----- > From: "Jonathan Griffin" <jgrif...@mozilla.com> > To: dev-b2g@lists.mozilla.org > Cc: "Lucas Adamski" <ladam...@mozilla.com>, "Ryan Vandermeulen" > <rya...@gmail.com> > Sent: Tuesday, July 23, 2013 12:32:30 PM > Subject: [b2g] mochitests randomly timing out > > We're seeing a frequent problem in which a random mochitest will take > orders of magnitude longer to execute than it normally does, causing the > testrun to timeout. > > For example, in this log, the test > "/tests/content/html/content/test/test_track_disabled.html" takes 4635ms > to complete: > > https://tbpl.mozilla.org/php/getParsedLog.php?id=25576635&tree=Mozilla-Inbound&full=1 > > However, in this log, the same test takes 331391ms to complete, which > results in a timeout: > > https://tbpl.mozilla.org/php/getParsedLog.php?id=25575730&tree=Mozilla-Inbound&full=1 > > Does anyone have any idea why this might be happening? Is it a > GC-related issue, and if so, is there any way to make our tests handle > this more gracefully? We could increase the mochitest timeout by a > significant factor, but would this just be hiding a real problem? > > Thanks, > > Jonathan > > > > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
