Closed Bug 1181446 Opened 9 years ago Closed 9 years ago

Intermittent TEST-UNEXPECTED-FAIL | dom/html/test/test_fullscreen-api-race.html | Test timed out.

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox40 --- unaffected
firefox41 --- unaffected
firefox42 --- fixed
firefox-esr38 --- unaffected

People

(Reporter: xidorn, Assigned: xidorn)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

No description provided.
Summary: TEST-UNEXPECTED-FAIL | dom/html/test/test_fullscreen-api-race.html | Test timed out. → Intermittent TEST-UNEXPECTED-FAIL | dom/html/test/test_fullscreen-api-race.html | Test timed out.
Note that, the Linux 64bit ones (comment 1 and comment 2) and the Windows 64bit ones (comment 3 and comment 4) are actually different thing. Timeout in comment 1 and comment 2 are on subtest "openNewTab, navigate", while that in comment 3 and comment 4 are on "openNewWindow, navigate". We also had some problem with "openNewWindow, navigate" subtest on Linux 32bit, where we disabled the specific subtest in bug 1180574 because of high frequency. This probably indicates that we do have some kind of bug inside the Gecko code when we do navigation inside fullscreenchange event.
It seems to me this has been a perm-fail on Windows opt builds.
It seems in some cases, a window could get blurred immediately after the waitForFocus call finishes... I have no idea how that could happen (and only on Windows opt builds), but it seems using flaky timeout could solve this issue... I hope I won't use that, but...
Attached patch patch (deleted) — — Splinter Review
Assignee: nobody → quanxunzhen
Attachment #8639679 - Flags: review?(bugs)
Comment on attachment 8639679 [details] [diff] [review] patch Any idea why we get the error? Because of not having focus? r+ anyhow. (and I can't wait us to remove the prefixes for this stuff.)
Attachment #8639679 - Flags: review?(bugs) → review+
url: https://hg.mozilla.org/integration/mozilla-inbound/rev/95b0a225ed1d1e055a276d0d27d2d5256cc00f31 changeset: 95b0a225ed1d1e055a276d0d27d2d5256cc00f31 user: Xidorn Quan <quanxunzhen@gmail.com> date: Wed Jul 29 08:59:59 2015 +1000 description: Bug 1181446 - Retry requesting fullscreen one more time if it fails initially on fullscreen-api-race test. r=smaug
(In reply to Olli Pettay [:smaug] from comment #177) > Comment on attachment 8639679 [details] [diff] [review] > patch > > Any idea why we get the error? Because of not having focus? Yes, not having focus. It seems that the main browser window takes the focus again immediately after the newly-opened one gets the focus and returns from waitForFocus. But what causes this re-focus is unknown.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
The failure in comment 324 again happens after we call requestFullscreen, which indicates a real bug that we fail to respond a fullscreen request with either fullscreenchange or fullscreenerror, which is pretty bad. It definitely needs further investigation, but should be in a different bug.
Blocks: 1189200
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: