Closed Bug 794400 Opened 12 years ago Closed 12 years ago

Failure in /ide@seleniumhq.org/tests/testCommands/testAlert/testAssertAlertFails.js | Timeout waiting for page loaded

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Platform:
All
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox18 affected, firefox19 affected, firefox20 affected, firefox21 affected, firefox-esr10 wontfix)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox18 --- affected
firefox19 --- affected
firefox20 --- affected
firefox21 --- affected
firefox-esr10 --- wontfix

People

(Reporter: AlexLakatos, Assigned: davehunt)

References

(
URL
)

Details

(Whiteboard: [mozmill-test-failure])

TEST: testAssertAlertFails.js::setupModule ERROR: controller.waitForPageLoad(): Timeout waiting for page loaded. WHEN: 09-25-2012 FIRST: 09-25-2012 FREQ: 1
The failure appears to be similar to bug 790191 as it's occurring in the closeAllTabs method.
We reverted to about:blank on bug 764782. So this should not happen anymore.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
No longer depends on: 790191
Looks like this is independent given the test failure from this evening: http://mozmill-ci.blargon7.com/#/addons/report/2e7486a8c08b5541b9074117e0699f85
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Dave, please investigate this problem. It seems to happen more often now.
Assignee: nobody → dave.hunt
Status: REOPENED → ASSIGNED
The failure indicates a timeout waiting for about:blank to load. Have we seen this anywhere else since we reverted to about:blank on bug 764782?
Last time happened yesterday, a day after the backout in bug 764782 http://mozmill-ci.blargon7.com/#/addons/report/2e7486a8c08b5541b9074117e0741fde
I've tried replicating this on a Windows 7 VM locally (the failure only occurs on Windows 7) without any luck. I watched a live testrun, which also did not fail. This failure has not occurred at all today. Next, I would like to try to replicate this on the VM that's showing the failure.
Happened again today on an x86 machine http://mozmill-ci.blargon7.com/#/addons/report/190d57cf64e3c5c3996c0c10598e874c
Hardware: x86_64 → All
On esr10 it's a bit different: Menu entry '#menuToolsSeleniumIDE' not found. http://mozmill-ci.blargon7.com/#/addons/report/190d57cf64e3c5c3996c0c1059ed7c4a Not sure why the menu entry cannot be found. I would assume a compatibility issue but then it should happen in each test.
status-firefox-esr10: --- → affected
Happened again yesterday on Nightly FR with Windows 7 32bit: http://mozmill-ci.blargon7.com/#/addons/report/674977957b923f4905160d1b9afad32f
status-firefox20: --- → affected
(In reply to Andrei Eftimie from comment #14) > Happened in 2012-12-30 on Win XP / Nightly: > http://mozmill-ci.blargon7.com/#/addons/report/ > 23d8fbdd0190d4b0496d6b129f07284d That doesn't look like the same issue.
(In reply to Dave Hunt (:davehunt) from comment #15) > (In reply to Andrei Eftimie from comment #14) > > Happened in 2012-12-30 on Win XP / Nightly: > > http://mozmill-ci.blargon7.com/#/addons/report/ > > 23d8fbdd0190d4b0496d6b129f07284d > > That doesn't look like the same issue. Created bug 826320 for it.
I've reproduced this locally in: WinXP under heavy load: http://mozmill-crowd.blargon7.com/#/addons/report/23d8fbdd0190d4b0496d6b129f59b947 OSX normal conditions: http://mozmill-crowd.blargon7.com/#/addons/report/23d8fbdd0190d4b0496d6b129f5947d4 Will investigate more to see if I can pinpoint the problem.
That's great! Really curious to see what's causing this.
I'm starting to think this is not related to selenium at all. We've seen this issue on and off on different tests. Appears to be more frequent lately (but I might have no good vision here, since I am new to this project). I've created bug 826693 , if we'll find out that it is indeed the case we might label this bug as a duplicate of bug 826693
Happened again on Firefox 20.0a2 (20.0a2, fr, 20130109042018): http://mozmill-ci.blargon7.com/#/addons/report/23d8fbdd0190d4b0496d6b129fe93407
Closing this as it hasn't happened recently. Please reopen if it occurs again. I suspect we'll find that this is indeed a duplicate of bug 826693.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.