Closed
Bug 936478
Opened 12 years ago
Closed 11 years ago
Test failure "controller.waitForPageLoad(): Timeout waiting for page loaded" in /testSecurity/testSafeBrowsingWarningPages.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P3)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cosmin-malutan, Assigned: danisielm)
References
()
Details
(Keywords: intermittent-failure, Whiteboard: [mozmill-test-failure])
Attachments
(4 files, 1 obsolete file)
2.04 KB,
patch
|
AndreeaMatei
:
review+
|
Details | Diff | Splinter Review |
2.16 KB,
patch
|
andrei
:
review+
andrei
:
checkin+
|
Details | Diff | Splinter Review |
2.19 KB,
patch
|
AndreeaMatei
:
review+
|
Details | Diff | Splinter Review |
2.22 KB,
patch
|
AndreeaMatei
:
review+
|
Details | Diff | Splinter Review |
This failed today on Windows and Linux with Nightly en many times in a short interval, and we could't reproduce it, so it's most likely a network issue being a remote test. We will watch to see if it fails again.
I will take a ci node down to check if it reproduces.
http://mozmill-daily.blargon7.com/#/remote/report/d17690a112360a2b3155acaa27d082ce
http://mozmill-daily.blargon7.com/#/remote/report/d17690a112360a2b3155acaa27d0ab86
http://mozmill-daily.blargon7.com/#/remote/report/d17690a112360a2b3155acaa27d1eb03
http://mozmill-daily.blargon7.com/#/remote/report/d17690a112360a2b3155acaa27d2a9d4
http://mozmill-daily.blargon7.com/#/remote/report/d17690a112360a2b3155acaa27d3378f
Reporter | ||
Comment 1•12 years ago
|
||
It didn't reproduce on the affected machine.
Comment 2•12 years ago
|
||
Some additional information.
The page where we get redirected from google:
http://safebrowsing.clients.google.com/safebrowsing/diagnostic?client=Firefox&hl=en-US&site=http://www.mozilla.org/firefox/its-an-attack.html
Looks different from the last time we saw it.
It could be that google recently (just now?) updated it we we caught some CDN refresh problems?
Comment 3•12 years ago
|
||
Another failure on 27, OSX, de:
http://mozmill-daily.blargon7.com/#/remote/report/2f1ca72938985fc4b989b7efcc37fa3c
status-firefox27:
--- → affected
Priority: -- → P3
Comment 4•12 years ago
|
||
This has failed lots of times today (~15 times)
We should try again to look into it.
Priority: P3 → P2
Updated•12 years ago
|
Assignee: nobody → mario.garbi
Updated•12 years ago
|
Status: NEW → ASSIGNED
Comment 5•12 years ago
|
||
I have tried to reproduce it on CI machines (XP and Linux) but without much luck, I will continue the investigation and hopefully I can witness a failure by observing the machines running remote testruns today.
Status: ASSIGNED → NEW
Comment 6•12 years ago
|
||
I wouldn't spend too much time on it given that we hopefully can upgrade to mozmill 2 soon.
Comment 7•12 years ago
|
||
I tried to reproduce this failure on the failing CI machines mm-win-8-64-3 and mm-ub-1304-4 and was not able even though the failured keep happening. This might be related to a Jenkins setting since by logging on the machine and triggering a testrun_remote script won't reproduce it even once.
Judging by Henrik's comment this might be fixed in Mozmill 2.0 and will focus on other bugs.
Comment 8•12 years ago
|
||
We need to get this skipped, way to many failures.
Attachment #8335867 -
Flags: review?(andreea.matei)
Comment 9•12 years ago
|
||
Comment on attachment 8335867 [details] [diff] [review]
skip.patch
Review of attachment 8335867 [details] [diff] [review]:
-----------------------------------------------------------------
Sorry, it's not applying anymore due to bug 905033.
Attachment #8335867 -
Flags: review?(andreea.matei) → review-
Updated•12 years ago
|
Status: NEW → ASSIGNED
Comment 10•12 years ago
|
||
Updated skip patch to apply cleanly again :)
Attachment #8335867 -
Attachment is obsolete: true
Attachment #8335930 -
Flags: review?(andreea.matei)
Comment 11•12 years ago
|
||
Comment on attachment 8335930 [details] [diff] [review]
skip_2.patch
Review of attachment 8335930 [details] [diff] [review]:
-----------------------------------------------------------------
Disabled:
http://hg.mozilla.org/qa/mozmill-tests/rev/b3fe63f861e0 (default)
Attachment #8335930 -
Flags: review?(andreea.matei) → review+
Comment 12•12 years ago
|
||
And aurora:
http://hg.mozilla.org/qa/mozmill-tests/rev/971bf49d48e6 (aurora)
Whiteboard: [mozmill-test-failure][mozmill-test-skipped]
Comment 13•11 years ago
|
||
I can still reproduce this on Aurora branch, I will investigate it and come with more info.
Comment 14•11 years ago
|
||
We've had this fail 3 times on ESR24:
http://mozmill-daily.blargon7.com/#/remote/report/94e33fe3d7ec0be6dbbfa0a702fcd47a
http://mozmill-daily.blargon7.com/#/remote/report/94e33fe3d7ec0be6dbbfa0a702fcb27f
http://mozmill-daily.blargon7.com/#/remote/report/94e33fe3d7ec0be6dbbfa0a702fd8bf0
status-firefox-esr24:
--- → affected
Updated•11 years ago
|
Assignee: mario.garbi → daniel.gherasim
Assignee | ||
Comment 15•11 years ago
|
||
This is a remote test and I run it today for 500 times on latest nightly with Windows 8.1. No failure at all.
My guess here is that it fails sometimes when accessing https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work?as=u&utm_source=inproduct because of the
ssl.google-analytics service timeout. I now that's a known issue with that service.
With the new Mozmill version we can find out exactly what's failing, so let's get it unskipped and see how it's running.
This skip patch applies cleanly on nightly and aurora.
Attachment #8399425 -
Flags: review?(andrei.eftimie)
Attachment #8399425 -
Flags: review?(andreea.matei)
Comment 16•11 years ago
|
||
We wont see if Ajax requests are hanging.
Comment 17•11 years ago
|
||
Failed 3 times with Beta 29.0b4 en-US, at waiting for about:blank it appears, this is the line affected:
http://hg.mozilla.org/qa/mozmill-tests/file/mozilla-beta/firefox/tests/remote/testSecurity/testSafeBrowsingNotificationBar.js#l119
This is not disabled on beta anymore, I guess do to the merge.
Summary: Test failure "controller.waitForPageLoad(): Timeout waiting for page loaded" /testSecurity/testSafeBrowsingWarningPages.js → Test failure "controller.waitForPageLoad(): Timeout waiting for page loaded (URI=about:blank, readyState=uninitialized)" in /testSecurity/testSafeBrowsingWarningPages.js
Comment 18•11 years ago
|
||
So this might be because when a new tab gets opened about:blank is the first page which gets loaded, and replaced right after with the target page. Is that something we can create a minimized testcase for to get it reproduced? Wouldn't we have to wait for the new tab being opened first?
Assignee | ||
Comment 19•11 years ago
|
||
(In reply to Andreea Matei [:AndreeaMatei] from comment #17)
> Failed 3 times with Beta 29.0b4 en-US, at waiting for about:blank it
> appears, this is the line affected:
> http://hg.mozilla.org/qa/mozmill-tests/file/mozilla-beta/firefox/tests/
> remote/testSecurity/testSafeBrowsingNotificationBar.js#l119
I can see that this is another test then the one from this bug's title.
Comment 20•11 years ago
|
||
Oh, you're right, my bad. I'll open a new bug for this and eventually make it general for "about:blank" failures.
Summary: Test failure "controller.waitForPageLoad(): Timeout waiting for page loaded (URI=about:blank, readyState=uninitialized)" in /testSecurity/testSafeBrowsingWarningPages.js → Test failure "controller.waitForPageLoad(): Timeout waiting for page loaded" in /testSecurity/testSafeBrowsingWarningPages.js
Comment 21•11 years ago
|
||
Comment on attachment 8399425 [details] [diff] [review]
bug_936478_unskip.patch
Review of attachment 8399425 [details] [diff] [review]:
-----------------------------------------------------------------
Let's unskip on default and see if we're still seeing failures.
Unskipped:
http://hg.mozilla.org/qa/mozmill-tests/rev/5b5d72d07722 (default)
Attachment #8399425 -
Flags: review?(andrei.eftimie)
Attachment #8399425 -
Flags: review?(andreea.matei)
Attachment #8399425 -
Flags: review+
Attachment #8399425 -
Flags: checkin+
Updated•11 years ago
|
Assignee | ||
Comment 22•11 years ago
|
||
In another 500 runs on windows 8.1 and 100 on Mac OSX 10.6 I haven't seen any failure.
Assignee | ||
Updated•11 years ago
|
Comment 23•11 years ago
|
||
What are we waiting for here? I see no action since April 1st.
Comment 24•11 years ago
|
||
Transplanted:
http://hg.mozilla.org/qa/mozmill-tests/rev/9a4d1b030cd7 (mozilla-aurora)
Daniel, please backport this patch on the rest of the branches.
Flags: needinfo?(daniel.gherasim)
Assignee | ||
Comment 25•11 years ago
|
||
The 1st unskip patch applies cleanly on aurora.
Here is the patch for beta, will come with another one for release.
On ESR the test is not disabled.
Testrun reports:
- UBUNTU 12.04 -
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e417707e5
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e41770a53
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e417711c9
- WINDOWS 8.1 -
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e4177439c
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e41775149
- MAC OSX 10.6 -
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e417712ec
http://mozmill-crowd.blargon7.com/#/remote/report/7ab760e27012969ae02e3b9e4177175f
Attachment #8403803 -
Flags: review?(andrei.eftimie)
Attachment #8403803 -
Flags: review?(andreea.matei)
Assignee | ||
Comment 26•11 years ago
|
||
Unskip patch for release.
Attachment #8403805 -
Flags: review?(andrei.eftimie)
Attachment #8403805 -
Flags: review?(andreea.matei)
Flags: needinfo?(daniel.gherasim)
Comment 27•11 years ago
|
||
Comment on attachment 8403803 [details] [diff] [review]
bug_936478_unskip_beta.patch
Review of attachment 8403803 [details] [diff] [review]:
-----------------------------------------------------------------
Please make sure to have the bug number mentioned in the commit messages.
Pushed:
http://hg.mozilla.org/qa/mozmill-tests/rev/993f25aa9e28 (beta)
Attachment #8403803 -
Flags: review?(andrei.eftimie)
Attachment #8403803 -
Flags: review?(andreea.matei)
Attachment #8403803 -
Flags: review+
Comment 28•11 years ago
|
||
Comment on attachment 8403805 [details] [diff] [review]
bug_936478_unskip_release.patch
Review of attachment 8403805 [details] [diff] [review]:
-----------------------------------------------------------------
Pushed:
http://hg.mozilla.org/qa/mozmill-tests/rev/d49557ae0b30 (release)
Attachment #8403805 -
Flags: review?(andrei.eftimie)
Attachment #8403805 -
Flags: review?(andreea.matei)
Attachment #8403805 -
Flags: review+
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure]
Comment 29•11 years ago
|
||
This still fails from time to time.
In the last 2 months we have 34 failures on the release branch:
http://mozmill-release.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-10-01&to=2014-11-25&test=%2FtestSecurity%2FtestSafeBrowsingWarningPages.js&func=testWarningPages
Similar failure rate on daily runs:
http://mozmill-daily.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-10-01&to=2014-11-25&test=%2FtestSecurity%2FtestSafeBrowsingWarningPages.js&func=testWarningPages
Status: RESOLVED → REOPENED
status-firefox27:
wontfix → ---
status-firefox28:
fixed → ---
status-firefox29:
fixed → ---
status-firefox30:
fixed → ---
status-firefox31:
fixed → ---
status-firefox33:
--- → affected
status-firefox34:
--- → affected
status-firefox35:
--- → affected
status-firefox36:
--- → affected
status-firefox-esr24:
fixed → ---
status-firefox-esr31:
--- → affected
Keywords: intermittent-failure
Priority: P2 → P3
Resolution: FIXED → ---
Comment 30•11 years ago
|
||
Please do not reopen bugs which have been fixed a long time ago. Create new ones instead. They are cheap. Sadly I cannot revert the status flags.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
status-firefox33:
affected → ---
status-firefox34:
affected → ---
status-firefox35:
affected → ---
status-firefox36:
affected → ---
status-firefox-esr31:
affected → ---
Resolution: --- → FIXED
Comment 31•11 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #30)
> Please do not reopen bugs which have been fixed a long time ago. Create new
> ones instead. They are cheap. Sadly I cannot revert the status flags.
This bug was not fixed. Should have been closed with WFM. Those flags only reflect disabled status.
Test was unskipped in April, we have failures from April up until now.
Comment 32•11 years ago
|
||
Oh, I see. But please open a new bug. This one has already about 30 comments and will only confuse.
Updated•6 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
•