Closed Bug 1349929 Opened 3 years ago Closed 2 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | /webdriver/actions/sequence.py | expected OK

Categories

(Testing :: web-platform-tests, defect)

Version 3
defect
Not set

Tracking

(firefox57 fixed)

RESOLVED FIXED
mozilla57
Tracking Status
firefox57 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: ato)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])

Attachments

(1 file)

the failure rate here has increased significantly starting August 31, primarily on linux64 opt and pgo:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1349929

:ato, I believe you have been working on the webdriver stuff recently, can you look into this and help get this resolved sometime in the next week or two?
Flags: needinfo?(ato)
Whiteboard: [stockwell needswork]
(In reply to Joel Maher ( :jmaher) (UTC-5) from comment #8)

> the failure rate here has increased significantly
> starting August 31, primarily on linux64 opt and pgo:
> https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=134
> 9929
> 
> :ato, I believe you have been working on the webdriver stuff
> recently, can you look into this and help get this resolved
> sometime in the next week or two?

I don’t think there’s anything more fishy going on here than the
fact that something, somewhere has gotten a tiny little bit slower.
The sequence.py test has always been close to the default wdspec
test timeout.  Expanding its timeout to the default long timeout is
reasonable.
Assignee: nobody → ato
Status: NEW → ASSIGNED
Flags: needinfo?(ato)
On my system sequence.py takes only about ~15s to run:

> 5.23u 0.72s 15.29r 	 ./mach wpt testing/web-platform/tests/webdriver/tests/actions/sequence.py  # status=1

However, I can easily imagine how it would be twice that in CI.
Comment on attachment 8904244 [details]
Bug 1349929 - Increase action sequence test timeout.

https://reviewboard.mozilla.org/r/176024/#review181348
Attachment #8904244 - Flags: review?(mjzffr) → review+
Pushed by atolfsen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/43ad1b32e0e3
Increase action sequence test timeout. r=maja_zf
https://hg.mozilla.org/mozilla-central/rev/43ad1b32e0e3
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
It's still showing up, e.g. twice in 8 runs in https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=a4252412b1ac3b90d0845e7c8af5f8231d4e8bce&filter-searchStr=wdspec
Do you want a new bug or should this one get reopened?
Flags: needinfo?(ato)
That’s odd.  I wonder if it has something to do with wptserve not
responding now that the tests no longer use inline data URIs.

Could you please file a new bug since I seem to have spoiled this
one with a patch?
Flags: needinfo?(ato) → needinfo?(aryx.bugmail)
Flags: needinfo?(aryx.bugmail)
Whiteboard: [stockwell needswork] → [stockwell unknown]
You need to log in before you can comment on or make changes to this bug.