Closed Bug 941575 Opened 6 years ago Closed Last year

Intermittent browser_fullscreen-window-open.js | Don't change window.innerWidth. - Got 1600, expected 1200

Categories

(Core :: Widget, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox31 --- disabled
firefox32 --- disabled
firefox33 --- disabled
firefox-esr24 --- unaffected

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure, Whiteboard: tpi:-)

Rev3 Fedora 12 mozilla-inbound debug test mochitest-browser-chrome on 2013-11-20 23:55:22 PST for push 22a26c92bf00

slave: talos-r3-fed-041

https://tbpl.mozilla.org/php/getParsedLog.php?id=30882520&tree=Mozilla-Inbound

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_fullscreen-window-open.js | Don't change window.innerWidth. - Got 1600, expected 1200
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_fullscreen-window-open.js | Don't change window.innerHeight. - Got 1200, expected 834
This is happening pretty frequently. Any chance you could take a look please? :)
Flags: needinfo?(saneyuki.s.snyk)
These testcase checks that the browser's fullscreen mode should open a popup in a new tab, and this failed case aim to checks that the tab's content width & height is valid.


I think we have some approach:
- At all, this testcase's approach may be _wrong_ (need not do in these testcases).
  - Thus we'll remove this case.
  - Or replace it with more suitable approach. (But I don't know the more good way...)
- This behavior is disable on Linux/Win by default. Thus I feel we'll be able to disable these testcases.

Personally I'd like to remove this failed case if it's no problem.
However, I want to hear bz's comment.
Flags: needinfo?(saneyuki.s.snyk) → needinfo?(bzbarsky)
I'm not following what the question is.  Are you asking me whether it's ok to just remove the test coverage?  Why do we want to do that, as opposed to fixing the test (if the test is wrong) or the code (if the code is wrong)?
Flags: needinfo?(bzbarsky) → needinfo?(saneyuki.s.snyk)
Summary: Intermittent TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_fullscreen-window-open.js | Don't change window.innerWidth. - Got 1600, expected 1200 → Intermittent browser_fullscreen-window-open.js | Don't change window.innerWidth. - Got 1600, expected 1200
I think it's time to consider disabling this test as it's happening with very high frequency and has gone months without any substantive activity towards fixing it.