Closed
Bug 1062330
Opened 10 years ago
Closed 7 years ago
Test Failure 'controller.waitForPageLoad(URI=https://www.stopbadware.org/firefox *, readyState=loading)' in /testSecurity/testSafeBrowsingNotificationBar.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)
Tracking
(firefox35 disabled, firefox36 disabled, firefox37 disabled, firefox38 fixed, firefox-esr31 disabled)
People
(Reporter: tracy, Assigned: mihaelav)
References
()
Details
(Whiteboard: [mozmill-test-failure][mozmill-test-skipped][sprint])
Attachments
(1 file)
1.09 KB,
patch
|
AndreeaMatei
:
review+
|
Details | Diff | Splinter Review |
Reporting this failure from beta_remote run in /testSecurity/testSafeBrowsingNotificationBar.js http://mozmill-release.blargon7.com/#/remote/report/12a8568e34c97b929089c7a61fc3331e
Reporter | ||
Comment 1•10 years ago
|
||
similar? http://mozmill-release.blargon7.com/#/remote/report/12a8568e34c97b929089c7a61fc00faf
Comment 2•10 years ago
|
||
10 min apart. possible network issues on either end.
Comment 3•10 years ago
|
||
Yeah. Page is still in loading state after 30s. So I also highly suspect a network issue here.
Comment 4•10 years ago
|
||
Failed for 54 times, non-reproducible. http://mozmill-release.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-10-01&to=&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testNotificationBar
Comment 5•10 years ago
|
||
We still see this failing regularly. If the server is responding but slowly we might be able to reduce this by increasing the timeout. A bit hard to track due to other issues affecting this test: http://mozmill-release.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-09-01&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testNotificationBar
Summary: Test Failure controller.waitForPageLoad(URI=https://www.stopbadware.org/firefox?hl=el&url=https%3A%2F%2Fwww.itisatrap.org%2Ffirefox%2Fits-an-attack.html, readyState=loading) → Test Failure 'controller.waitForPageLoad(URI=https://www.stopbadware.org/firefox*, readyState=loading)' in /testSecurity/testSafeBrowsingNotificationBar.js
Comment 6•10 years ago
|
||
Bumping priority. This is failing in 2 ways: > controller.waitForPageLoad(URI=about:blank, readyState=uninitialized) and > controller.waitForPageLoad(URI=https://www.stopbadware.org/firefox?hl=uk&url=https%3A%2F%2Fwww.itisatrap.org%2Ffirefox%2Fits-an-attack.html, readyState=loading)
Priority: -- → P2
Updated•10 years ago
|
status-firefox33:
--- → affected
status-firefox34:
--- → affected
status-firefox35:
--- → affected
status-firefox36:
--- → affected
Comment 7•10 years ago
|
||
I'd like to disable this test for now. This is really unreliable and is constantly failing. This applies to default, mozilla-aurora and mozilla-beta
Attachment #8511083 -
Flags: review?(andreea.matei)
Comment 8•10 years ago
|
||
Comment on attachment 8511083 [details] [diff] [review] skip.patch Review of attachment 8511083 [details] [diff] [review]: ----------------------------------------------------------------- Looks good.
Attachment #8511083 -
Flags: review?(andreea.matei) → review+
Comment 9•10 years ago
|
||
Disabled: https://hg.mozilla.org/qa/mozmill-tests/rev/73fbffab24c8 (default) https://hg.mozilla.org/qa/mozmill-tests/rev/18126d037e8b (mozilla-aurora) https://hg.mozilla.org/qa/mozmill-tests/rev/2b3167614438 (mozilla-beta) We don't expect another 33 build for a while. If we don't have any updates here until then, we might also disable it for the next one.
Comment 10•10 years ago
|
||
bug 1071515 comment 18, let's get this skip backported on release too!
Comment 11•10 years ago
|
||
Ugh, I was optimistic. Had a new release build, failed and crashed a lot, disabled as well: https://hg.mozilla.org/qa/mozmill-tests/rev/5da4a715fadb (mozilla-release)
Comment 12•10 years ago
|
||
Failed a lot on ESR31 in the last couple of days. Transplanted the skip: https://hg.mozilla.org/qa/mozmill-tests/rev/d9a27f38e87d (mozilla-esr31)
status-firefox-esr31:
--- → disabled
Keywords: intermittent-failure
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped]
Assignee | ||
Updated•9 years ago
|
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure][mozmill-test-skipped][sprint]
Assignee | ||
Comment 13•9 years ago
|
||
I couldn't reproduce this locally (Win 8.1 64bit VM) nor on staging (Win 8.1 x86). http://mozmill-crowd.blargon7.com/#/remote/reports?app=All&branch=38&platform=Win&from=2015-01-29&to=2015-01-30
Assignee | ||
Comment 14•9 years ago
|
||
I think we can unskip this now.
Updated•9 years ago
|
Assignee: nobody → mihaela.velimiroviciu
Comment 15•9 years ago
|
||
Lets see: https://hg.mozilla.org/qa/mozmill-tests/rev/12f048f0c643 (default)
status-firefox33:
disabled → ---
status-firefox34:
disabled → ---
status-firefox37:
--- → disabled
status-firefox38:
--- → fixed
Updated•9 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 16•9 years ago
|
||
The test hasn't failed since it was un-skipped. Maybe we should enable it on the other branches, as well.
Comment 17•9 years ago
|
||
Removing keyword, since it's intended for test failures that are seen on Treeherder (and otherwise you'll end up with bugs being marked as worksforme if no occurrences are seen on Treeherder). Let me know if you want a new keyword created for intermittent mozmill failures :-)
Keywords: intermittent-failure
Comment 18•9 years ago
|
||
(In reply to Ed Morley [:emorley] from comment #17) > Let me know if you want a new keyword created for intermittent mozmill > failures :-) Mozmill tests are dead, and their replacement Marionette (Firefox UI) tests will report to treeherder (soon).
Comment 19•9 years ago
|
||
Ah, thank you
Comment 20•7 years ago
|
||
Mozmill tests have been superseded by Marionette tests.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•