Some of our security tests are failing in the waitForPageLoad() call. http://mozmill-ci.blargon7.com/#/functional/report/fdec829b93b19c73985be1d38842b38d We should use the pages from mozqa.com instead. That work has to happen on bug 661121.

My suggestion is to use https://www.mozilla.org/en-US/ for the failures above.

(In reply to Remus Pop (:RemusPop) from comment #2) > My suggestion is to use https://www.mozilla.org/en-US/ for the failures > above. No, please see bug 661121 how it has to be solved.

testAddMozSearchProvider.js::testAddMozSearchPlugin is also failing for this same reason on Firefox 15.0 beta 3 http://mozmill-ci.blargon7.com/#/functional/report/c77cfb8878087b850538b93cf20f90ad.

Ioana: That is not a security test. Please file the failure as a separate bug. Also, are you able to replicate the failure?

(In reply to Dave Hunt (:davehunt) from comment #5) > Ioana: That is not a security test. Please file the failure as a separate > bug. Also, are you able to replicate the failure? My bad, Dave. Since the bug has no security flags or whiteboard tags, I tought this bug could be used for more failures with the same error. Anyway, I filed a new bug: bug 779488. I haven't been able to try and reproduce the issue locally yet because I don't have the necessary environment set on Windows. I will update bug 779488 as soon as I get to do that.

This happens on and off without anything we could trace down to a specific reason. We would need at least get it to reproduced.

This is happening again over testSafeBrowsingNotificationBar.js and testSafeBrowsingWarningPages.js, only on Mac OS X with Mozmill 1.5.19 and Nightly branch. Reports: * http://mozmill-ci.blargon7.com/#/functional/failure?branch=18.0&platform=Mac&from=2012-10-01&to=2012-10-08&test=%2FtestSecurity%2FtestSafeBrowsingWarningPages.js&func=testSafeBrowsingWarningPages.js%3A%3AtestWarningPages * http://mozmill-ci.blargon7.com/#/functional/failure?branch=18.0&platform=Mac&from=2012-10-01&to=2012-10-08&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testSafeBrowsingNotificationBar.js%3A%3AtestNotificationBar

I'm fairly sure that's related to the goButton issue on bug 790191 which we really, really have to fix.

(In reply to Henrik Skupin (:whimboo) from comment #10) > I'm fairly sure that's related to the goButton issue on bug 790191 which we > really, really have to fix. I don't think so because it does not fail in the setupModule due to tabs.closeAllTabs() I will look into those tests also today see If the reproduce steps are similar to testGoButton.js failure still.

Ah, right. It fails later when opening one of the bad sites.

So no more failures in the last week. I will close the bug for now but lets reopen if it starts to happen again.

Started happening again on Linux x86 with Aurora FR: http://mozmill-ci.blargon7.com/#/functional/report/72e15dc943833b8fcba70aeb51338aa8 And Linux x64 with Beta en-US: http://mozmill-ci.blargon7.com/#/functional/report/72e15dc943833b8fcba70aeb512c39cf

It's not worth keeping individual bugs open for that issue. We have to investigate it across tests whether if those are local or remote. Therefore we have bug 826693.