Closed Bug 1361339 Opened 7 years ago Closed 6 years ago

Intermittent test_modal_dialogs.py TestTabModalAlerts.test_alert_accept | TimeoutException: Timed out after 5.0 seconds

Categories

(Testing :: Marionette Client and Harness, defect)

Version 3
All
Windows 10
defect
Not set
normal

Tracking

(firefox56 affected)

RESOLVED WORKSFORME
Tracking Status
firefox56 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])

It fails in the alert_present wait:

1493718933043	Marionette	TRACE	21 -> [0,16,"findElement",{"using":"id","value":"tab-modal-alert"}]
1493718933049	Marionette	TRACE	21 <- [1,16,null,{"value":{"element-6066-11e4-a52e-4f735466cecf":"f425de3a-592c-4a14-9012-b6a85e0fcc06","ELEMENT":"f425de3a-592c-4a14-9012-b6a85e0fcc06"}}]
1493718933050	Marionette	TRACE	21 -> [0,17,"clickElement",{"id":"f425de3a-592c-4a14-9012-b6a85e0fcc06"}]
1493718933347	Marionette	DEBUG	Canceled page load listener because no navigation has been detected
1493718933348	Marionette	TRACE	21 <- [1,17,null,{}]
1493718933351	Marionette	TRACE	21 -> [0,18,"getTextFromDialog",{}]

So the click was successful, but the alert did never show up.
It's clearly a Windows 10 only test failure.
OS: Unspecified → Windows 10
Hardware: Unspecified → All
this is primarily on pgo and autoland, odd why we don't see this as often on mozilla-inbound.
Whiteboard: [stockwell unknown]
Haven’t seen this in a while.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.