1000090 - Test failures with "controller.waitForPageLoad(URI=about:newtab|blank, readyState=complete|unintialized)"

Status: RESOLVED INVALID

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

Description

[Daniel Gherasim]

We've seen failures across different tests with waitForPageLoad where the URL we are waiting for it's self-served like "about:newtab" or "about:blank" on different states.

We should get this fixed in the future. But first, let's make a summary here of the tests are failing and how often they did this year.

> /remote/testLayout/testNavigateFTP.js
Messsage: controller.waitForPageLoad(URI=about:newtab, readyState=complete)
Times failed: ~80

> /remote/testSecurity/testSafeBrowsingNotificationBar.js
controller.waitForPageLoad(URI=about:blank, readyState=uninitialized)
Times failed: ~20

> /endurance/testBookmarks_OpenAndClose/test1.js
Message: controller.waitForPageLoad(URI=about:newtab, readyState=complete)
http://mozmill-daily.blargon7.com/#/endurance/report/97976110c92e838016d17f7fb24ca845

This is what I found so far, once we get other failures we can update this.

Comment 1

[Andrei Eftimie]

We should really get to the bottom of this.

Comment 2

[Cosmin Malutan, [:cosmin-malutan]]

This failed again on Ubuntu 13.10 with Aurora ru:
http://mozmill-daily.blargon7.com/#/remote/report/44e0169acb64b68a44c1ad880b00d13b
I couldn't reproduce this neither by running the test alone or a compleat testrun.

Comment 3

[Cosmin Malutan, [:cosmin-malutan]]

Failed for 10 times in the past month, it looks like all are network issues:
http://mozmill-daily.blargon7.com/#/remote/failure?app=Firefox&branch=All&platform=All&from=2014-05-12&to=&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testNotificationBar

Comment 4

[Andrei Eftimie]

We shouldn't have "network" issues on "about:blank" and "about:newtab"...

Comment 5

[Daniel Gherasim]

We shouln't have network issues on loading local pages either.
Some updates here, this issue is affecting lot of our testruns lately, especially in 

> /testPreferences/testRestoreHomepageToDefault.js
> /testPreferences/testSetToCurrentPage.js
> /testToolbar/testHomeButton.js

http://mozmill-daily.blargon7.com/#/functional/report/6959f9a823696109676338908348349c
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a8236961096763389083482ad5
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a823696109676338908349d8f1
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a823696109676338908349d51d
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a82369610967633890835d2584
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a82369610967633890835d1f0b
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a8236961096763389083613eda
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a8236961096763389083613caf
http://mozmill-daily.blargon7.com/#/functional/report/6959f9a8236961096763389083782d08

Please check:

http://mozmill-daily.blargon7.com/#/functional/failure?app=All&branch=All&platform=All&from=2014-02-03&test=%2FtestPreferences%2FtestRestoreHomepageToDefault.js&func=testRestoreHomeToDefault

http://mozmill-daily.blargon7.com/#/functional/failure?app=All&branch=All&platform=All&from=2014-02-03&test=%2FtestPreferences%2FtestSetToCurrentPage.js&func=testSetHomePage

http://mozmill-daily.blargon7.com/#/functional/failure?app=All&branch=All&platform=All&from=2014-02-03&test=%2FtestToolbar%2FtestHomeButton.js&func=testHomeButton

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

We can have timeout issues locally when the HTTPd.js server as run, is not correctly sending the response. This might happen due to several reasons, but also if a Firefox instance is still open and doesn't shutdown correctly. Sometimes we leave a zombie process behind, which could still have a handle to the used port. But that is not operating anymore.

I think that only bug 754847 might be able to help us here.

Comment 7

[Daniel Gherasim]

Failed 5 times today:
http://mozmill-release.blargon7.com/#/remote/failure?app=All&branch=All&platform=All&from=2014-07-01&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testNotificationBar

Comment 8

[Teodor Druta]

Attachment: newtabtestcase.patch

I have encountered this issue working on a about:newtab page in content class, it seems that calling waitForPageLoad after opening about:newtab fails intermittently usually with Test failure "controller.waitForPageLoad(URI=about:newtab, readyState=complete)" message.

Here is the dump results from mozmill windows.js module:
Success: http://pastebin.com/ffhWWm9G
Failure: http://pastebin.com/qnAELmzv

Also I have attached my simplified testcase which I used to investigate this.

Comment 9

[Teodor Druta]

(In reply to Teodor Druta from comment #8)
> Created attachment 8547494 [details] [diff] [review]
> newtabtestcase.patch
> 
> I have encountered this issue working on a about:newtab page in content
> class, it seems that calling waitForPageLoad after opening about:newtab
> fails intermittently usually with Test failure
> "controller.waitForPageLoad(URI=about:newtab, readyState=complete)" message.
> 
> Here is the dump results from mozmill windows.js module:
> Success: http://pastebin.com/ffhWWm9G
> Failure: http://pastebin.com/qnAELmzv
> 
> Also I have attached my simplified testcase which I used to investigate this.

This specific issue I have reported is related to Bug 1120906.

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Comment on attachment 8547494 [details] [diff] [review]
newtabtestcase.patch

I assume this makes this testcase obsolete then.

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Mozmill tests have been superseded by Marionette tests.