Closed Bug 823022 Opened 12 years ago Closed 9 years ago

intermittent failures in docshell/test/test_bug590573.html | test 8, got 300 for popup.scrollY instead of 199|200 - got 1, expected 0 | test 10, got 300 for popup.scrollY instead of 199|200 - got 1, expected 0

Categories

(Core :: DOM: Navigation, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jfkthame, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=18088722&tree=Firefox

16183 ERROR TEST-UNEXPECTED-FAIL | /tests/docshell/test/test_bug590573.html | test 8, got 300 for popup.scrollY instead of 199|200 - got 1, expected 0
16185 ERROR TEST-UNEXPECTED-FAIL | /tests/docshell/test/test_bug590573.html | test 10, got 300 for popup.scrollY instead of 199|200 - got 1, expected 0
Remote Device Error: unable to connect socket: [Errno 111] Connection refused

Re-trigger on the same push came up green: intermittent.
(CCing Joel since Android 4.0)
seriously wtf, oh well- lets see how frequently this happens.
This explosion of instances brought to you by https://hg.mozilla.org/integration/mozilla-inbound/rev/8bac87268303 from bug 827836.
Blocks: 827836
wow, sounds like it is time to back that patch out.  If this was intended, then we need to fix the test asap.
So I was looking at this a little bit today. It's the first time I've looked into debugging a docshell test, and I figured the easiest way to do it was to make a standalone version of the test: http://people.mozilla.com/~kgupta/tmp/test_bug590573.html

This test passes if I load it my desktop FF. When I load it in Fennec though it shows this error in logcat:

E/GeckoConsole(31570): [JavaScript Error: "TypeError: opener is null" {file: "http://people.mozilla.com/~kgupta/tmp/file_bug590573_1.html" line: 1}]

Joel, do you know if I need to set any particular env variables or prefs to make this work?
:kats,

I have no idea why the opener would be null on Fennec.  There is nothing in the environment or prefs that I can think of.  Here are the prefs we set for our core mochitest automation:
http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in#372
Note that as of bug 827836's re-landing (i.e. cset 54f8e15ab698) the intermittent failures here may show up with "299" instead of "300" (as in comment 184). This is expected.
Disabled on Android for too many failures:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5f6033f1481f
Whiteboard: [test disabled on Android][leave open]
I can sometimes reproduce this error with: http://people.mozilla.org/~mwargers/mochitestjs2/test_bug590573.html
When after loading that testcase, I keep my finger on the phone screen, I constantly get these kind of errors.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Re-enabled on Android (4.3 emulator tests OK on try) via bug 821821.
Assignee: nobody → gbrown
Whiteboard: [test disabled on Android][leave open]
You need to log in before you can comment on or make changes to this bug.