Closed Bug 1160008 Opened 10 years ago Closed 9 years ago

Intermittent testVideoDiscovery,testOfflinePage,testUITelemetry,testAboutPasswords | GeckoEventExpecter - blockForEvent timeout: Robocop:JS

Categories

(Firefox for Android Graveyard :: Testing, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox40 affected)

RESOLVED DUPLICATE of bug 1184186
Tracking Status
firefox40 --- affected

People

(Reporter: philor, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure)

No description provided.
See Also: → 1094649
Summary: Intermittent testVideoDiscovery | GeckoEventExpecter - blockForEvent timeout: Robocop:JS → Intermittent testVideoDiscovery,testOfflinePage | GeckoEventExpecter - blockForEvent timeout: Robocop:JS
I'm guessing that the testOfflinePage spike is from bug 1151786.
Flags: needinfo?(mark.finkle)
Summary: Intermittent testVideoDiscovery,testOfflinePage | GeckoEventExpecter - blockForEvent timeout: Robocop:JS → Intermittent testVideoDiscovery,testOfflinePage,testUITelemetry | GeckoEventExpecter - blockForEvent timeout: Robocop:JS
Summary: Intermittent testVideoDiscovery,testOfflinePage,testUITelemetry | GeckoEventExpecter - blockForEvent timeout: Robocop:JS → Intermittent testVideoDiscovery,testOfflinePage,testUITelemetry,testAboutPasswords | GeckoEventExpecter - blockForEvent timeout: Robocop:JS
The testOfflinePage failures look like hangs, with promiseOffline() waiting to observe network:offline-status-changed. https://treeherder.mozilla.org/#/jobs?repo=try&revision=6343ee790276 re-creates the failures with extra logging in nsIOService::SetOffline to see if network:offline-status-changed is sent. Compare (failure) http://mozilla-releng-blobs.s3.amazonaws.com/blobs/try/sha512/f9f464bf19320813018b5d33614764132af7a951cb2542315a8ca1af88f353aee3f6a7e0fec32bdff961d47e090805a58dc100611c6055360c291394bd711af2 06-02 13:10:27.961 1600 1617 I Robocop : {"message":"Robocop:JS should equal Robocop:JS","time":1433275827949,"source":"robocop","status":"PASS","test":"testOfflinePage","thread":null,"subtest":"Given message occurred for registered event: {\"message\":\"\\nTEST-PASS | testOfflinePage.js | [test_offline : 95] Docshell URI is the original URI.\\n\",\"innerType\":\"progress\",\"type\":\"Robocop:JS\"}","action":"test_status","pid":null} 06-02 13:10:27.961 1600 1617 D Robocop : received event Robocop:JS 06-02 13:10:27.980 1600 1613 D Robocop : unblocked on expecter for Robocop:JS 06-02 13:10:28.001 1600 1613 I Robocop : {"message":"[test_offline : 95] Docshell URI is the original URI.","time":1433275827983,"source":"robocop","status":"PASS","test":"testOfflinePage","thread":null,"subtest":"testOfflinePage.js","action":"test_status","pid":null} 06-02 13:10:28.011 1600 1617 I Gecko : SetOffline: 0 06-02 13:10:28.131 1600 1617 D GeckoTabs: handleMessage: Tab:ViewportMetadata with (success) http://mozilla-releng-blobs.s3.amazonaws.com/blobs/try/sha512/2a1dc1ab072bf348e73c84a2dc74be9b32da7abe8a420331f31805dfce7ccc630ab59c10ff7874d6f97e7662af9a5ed160f366aed0a0720ecef0fef8d06b886a 06-02 13:17:33.523 1794 1802 I Robocop : {"message":"[test_offline : 95] Docshell URI is the original URI.","time":1433276253523,"source":"robocop","status":"PASS","test":"testOfflinePage","thread":null,"subtest":"testOfflinePage.js","action":"test_status","pid":null} 06-02 13:17:33.534 1794 1804 I Gecko : SetOffline: 0 06-02 13:17:33.534 1794 1804 I Gecko : SetOffline - notify online 06-02 13:17:33.553 1794 1804 D Robocop : handleMessage called for: Robocop:JS; expecting: Robocop:JS 06-02 13:17:33.563 1794 1804 I Robocop : {"message":"Robocop:JS should equal Robocop:JS","time":1433276253563,"source":"robocop","status":"PASS","test":"testOfflinePage","thread":null,"subtest":"Given message occurred for registered event: {\"message\":\"\\nTEST-INFO | testOfflinePage.js | Received topic: network:offline-status-changed\\n\",\"innerType\":\"progress\",\"type\":\"Robocop:JS\"}","action":"test_status","pid":null} SetOffline(0) is called in both cases, but in the failed tests, SetOffline does not send the notification...maybe because it thinks it is already online?
Failure: 06-02 13:10:05.712 1600 1617 I Gecko : SetOffline: 1 06-02 13:10:05.720 1600 1617 I Gecko : SetOffline - notify offline ... 06-02 13:10:23.262 1600 1617 I Gecko : SetOffline: 0 06-02 13:10:23.282 1600 1617 I Gecko : SetOffline - notify online ... 06-02 13:10:28.011 1600 1617 I Gecko : SetOffline: 0 Success: 06-02 13:17:20.724 1794 1804 I Gecko : SetOffline: 1 06-02 13:17:20.734 1794 1804 I Gecko : SetOffline - notify offline ... 06-02 13:17:33.534 1794 1804 I Gecko : SetOffline: 0 06-02 13:17:33.534 1794 1804 I Gecko : SetOffline - notify online
The "extra" online request seems to happen while the test is waiting for DOMContentLoaded at http://hg.mozilla.org/mozilla-central/annotate/e537a1ba501b/mobile/android/tests/browser/robocop/testOfflinePage.js#l89 Is there some kind of side-effect of the LoadURI call that causes us to go online? Or is there some independent event causing it?
Depends on: 1171303
After bug 1171303(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #39) > I'm guessing that the testOfflinePage spike is from bug 1151786. Indeed it was, kind of, and that has now been resolved via bug 1171303. The remaining cases are most typically testFilePicker (the first test in rc3) and testUITelemetry (the first test in rc4)...maybe some kind of start-up timing issue?
Flags: needinfo?(mark.finkle)
testUITelemetry is running well now. The remaining tests were re-written as mochitest-chrome tests in...
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.