Closed
Bug 1420167
Opened 7 years ago
Closed 7 years ago
Perma test-verify dom/vr/test/mochitest/test_vrController_displayId.html | Test timed out. - Test timed out.
Categories
(Core :: WebVR, defect, P5)
Core
WebVR
Tracking
()
RESOLVED
FIXED
mozilla59
Tracking | Status | |
---|---|---|
firefox59 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: kip)
References
Details
(Keywords: intermittent-failure, Whiteboard: [stockwell fixed:other])
Attachments
(1 file)
Filed by: csabou [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=147075874&repo=mozilla-central https://queue.taskcluster.net/v1/task/XesT4PsPTnGpwp-gjgBp_w/runs/0/artifacts/public/logs/live_backing.log
Comment 1•7 years ago
|
||
Test verification of test_vrController_displayId.html was triggered when the test was modified by bug 1407423; those changes have been backed out for other failures. On backout, test verification of test_vrController_displayId.html was triggered again, and failed again, on all platforms except Android.
See Also: → 1407423
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → kgilbert
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 4•7 years ago
|
||
is this still broken? no failures since November 23rd. :gbrown, how does test-verify know when to run and keep reporting errors?
Flags: needinfo?(gbrown)
Whiteboard: [stockwell needswork]
Comment 5•7 years ago
|
||
test-verify only runs when a test is modified. So we expect it to fail -- typically consistently and often on multiple platforms -- when the test is modified, and then to see no more failures unless the test is modified again. In this case, see comment 1: The test failed verification when it was modified, then the modification was backed out and it still failed verification. It apparently hasn't been modified since. It's easy to see this happening locally (I ran on Linux): mach mochitest dom/vr/test/mochitest/test_vrController_displayId.html is OK mach mochitest dom/vr/test/mochitest/test_vrController_displayId.html --verify consistently hangs on second iteration mach mochitest dom/vr/test/mochitest/test_vrController_displayId.html --repeat 2 consistently hangs on second iteration
Flags: needinfo?(gbrown)
Comment 6•7 years ago
|
||
in summary this test case will not pass test-verify by failing on the second time it is run in the same browser session.
Comment 7•7 years ago
|
||
Well, it can be reproduced via `./mach mochitest --repeat=5 dom/vr/test/mochitest/test_vrController_displayId.html`. I believe it could be a new regression from the recent multi-threading work.
Comment hidden (mozreview-request) |
Assignee | ||
Comment 9•7 years ago
|
||
mozreview-review |
Comment on attachment 8932747 [details] Bug 1420167 - Clean the current test system when creating a new VR test system; https://reviewboard.mozilla.org/r/203792/#review209552 This LGTM, thanks!
Attachment #8932747 -
Flags: review?(kgilbert) → review+
Comment 10•7 years ago
|
||
Pushed by dmu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bec19f67b06c Clean the current test system when creating a new VR test system; r=kip
Comment 11•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/bec19f67b06c
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox59:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Updated•7 years ago
|
Whiteboard: [stockwell needswork] → [stockwell fixed:other]
You need to log in
before you can comment on or make changes to this bug.
Description
•