Closed Bug 1317121 Opened 3 years ago Closed 6 months ago

Intermittent test_timeouts.py TestTimeouts.test_search_timeout_found_settimeout | NoSuchElementException: Unable to locate element: newDiv

Categories

(Testing :: Marionette, defect, P5)

All
Android
defect

Tracking

(firefox51 unaffected, firefox52 wontfix, firefox-esr52 unaffected, firefox53 disabled, firefox54 disabled, firefox55 disabled, firefox63 disabled, firefox64 disabled, firefox65 disabled, firefox66 disabled)

RESOLVED WONTFIX
Tracking Status
firefox51 --- unaffected
firefox52 --- wontfix
firefox-esr52 --- unaffected
firefox53 --- disabled
firefox54 --- disabled
firefox55 --- disabled
firefox63 --- disabled
firefox64 --- disabled
firefox65 --- disabled
firefox66 --- disabled

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

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

Attachments

(1 file)

Affected code here:

> button = self.marionette.find_element(By.ID, "createDivButton")
> button.click()
> self.marionette.set_search_timeout(8000)
> self.assertEqual(HTMLElement, type(self.marionette.find_element(By.ID, "newDiv")))

So a click on the createDivButton in test.html will delay the creation of the newDiv div by 2000ms. Maybe calling set_search_timeout was not successful here.
From gecko.log:

> 1479009963991	Marionette	TRACE	conn755 -> [0,8,"timeouts",{"implicit":8000}]
> 1479009963994	Marionette	TRACE	conn755 <- [1,8,null,{}]
> 1479009964007	Marionette	TRACE	conn755 -> [0,9,"findElement",{"using":"id","value":"newDiv"}]
[..]
> 1479009989855	Marionette	TRACE	conn755 <- [1,9,{"error":"no such element","message":"Unable to locate element: newDiv","stacktrace":""},null]

The timeout used here is 25852ms. What's going on here?
Flags: needinfo?(ato)
I don’t know.  I don’t have the bandwidth to look at this right now, but this is a likely contender for something to look at next.
Flags: needinfo?(ato)
Mass wontfix for bugs affecting firefox 52.
See Also: → 1306848
Assignee: nobody → gbrown
This looks just like bug 1306848 - let's handle it the same way.
Attachment #8855369 - Flags: review?(ato)
Attachment #8855369 - Flags: review?(ato) → review+
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/73125874d9b9
Skip TestTimeouts.test_search_timeout_found_settimeout on Android; r=ato
Assignee: gbrown → nobody
Keywords: leave-open
Whiteboard: [stockwell disabled]
Only preent on release in the last four months.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Sorry, this was just disabled on Android.
Status: RESOLVED → REOPENED
Keywords: test-disabled
OS: Unspecified → All
Priority: -- → P5
Hardware: Unspecified → All
Resolution: FIXED → ---
Version: Version 3 → Trunk
The leave-open keyword is there and there is no activity for 6 months.
:automatedtester, maybe it's time to close this bug?
Flags: needinfo?(dburns)
This appears to have been reenabled so closing
Flags: needinfo?(dburns)
Status: REOPENED → RESOLVED
Closed: 2 years ago10 months ago
Resolution: --- → FIXED
Assignee: nobody → gbrown
(In reply to David Burns :automatedtester from comment #20)
> This appears to have been reenabled so closing

We should have a look at the test file at least, which would have revealed that the test is still disabled:

https://searchfox.org/mozilla-central/rev/d35199ef15ffa57d190886e20d5df6471faf0870/testing/marionette/harness/marionette_harness/tests/unit/test_timeouts.py#48

Not sure if intermittent bugs are still being closed automatically even with the disabled keyword set. As such I will set leave-open again.
Assignee: gbrown → nobody
Status: RESOLVED → REOPENED
Keywords: leave-open
Resolution: FIXED → ---

We should be able to unskip this patch once we moved the Mn jobs to the new and faster Android 7.0 x86 emulator, which is done on bug 1500509.

Depends on: 1500509
OS: All → Android

We moved away from the ARM platform and this failure no longer occurs on packet.net with Android 7.0 x86_64.

Status: REOPENED → RESOLVED
Closed: 10 months ago6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.