1343520 - Intermittent test_direct_update.py TestDirectUpdate.test_update | InvalidArgumentException:

Status: RESOLVED FIXED

(Testing :: Firefox UI Tests, defect)

Description

[Treeherder Bug Filer]

Filed by: hskupin [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=80841496&repo=mozilla-central

https://firefox-ui-tests.s3.amazonaws.com/e28d6eb0-eb50-4163-be94-5a41c17b103f/log_info.log

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

There was a huge spike for nightly builds yesterday:

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=1bc2ad020aee2830e0a7941f10958dbec108c254&filter-searchStr=Firefox+&filter-tier=1&filter-tier=2&filter-tier=3

For today it looks a bit better. But I wonder where this is coming from...

> 04:56:06     INFO -  1488372966577	Marionette	TRACE	conn7 -> [0,3,"setTimeouts",{"pageLoad":300000}]
> 04:56:06     INFO -  1488372966580	Marionette	TRACE	conn7 <- [1,3,{"error":"invalid argument","message":"","stacktrace":"WebDriverError@chrome://marionette/content/error.js:160:5\nInvalidArgumentError@chrome://marionette/content/error.js:222:5\nfromJSON@chrome://marionette/content/session.js:72:17\nGeckoDriver.prototype.setTimeouts@chrome://marionette/content/driver.js:1508:19\nDispatcher.prototype.execute/req<@chrome://marionette/content/dispatcher.js:128:20\nTaskImpl_run@resource://gre/modules/Task.jsm:319:42\nTaskImpl@resource://gre/modules/Task.jsm:277:3\nasyncFunction@resource://gre/modules/Task.jsm:252:14\nTask_spawn@resource://gre/modules/Task.jsm:166:12\nDispatcher.prototype.execute@chrome://marionette/content/dispatcher.js:118:13\nDispatcher.prototype.onPacket@chrome://marionette/content/dispatcher.js:89:5\n_onJSONObjectReady/<@chrome://marionette/content/server.js -> resource://devtools/shared/transport/transport.js:483:11\nexports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14\nexports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14\n"},null]

So we fail in setting the timeout for page load correctly. And now I can remember for bug 1342162. So this is a regression visible a couple of days until funsize doesn't produce mar files anymore for builds which used the old property name. Given that the patch landed yesterday it will cause failures up to March 4th.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Actually this won't go away from itself. It will hit us when we have to do update tests for releases given that the patch on bug 1342162 will never allow us to run update tests from 52.0, and which is a blocker for QA. So I will request a backout of the patch, for a sane fix.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

The patch on bug 1342162 got backed out. So this should be fixed the next days. I will leave the bug open for an easier starring of failures on Treeherder until then.

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

thanks :whimboo for taking care of this and tracking it.

Comment 5

[Intermittent Failures Robot]

77 failures in 783 pushes (0.098 failures/push) were associated with this bug in the last 7 days. 

This is the #12 most frequent failure this week. 

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:
* mozilla-central: 77

Platform breakdown:
* windows8-64: 16
* windows7-64: 16
* windows8-32: 9
* windows7-32: 9
* osx-10-9: 7
* osx-10-11: 7
* osx-10-10: 7
* linux32: 4
* linux64: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1343520&startday=2017-02-27&endday=2017-03-05&tree=all

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Everything is back to normal for update tests on mozilla-central. Closing bug as fixed.