Open Bug 1790325 Opened 2 years ago Updated 3 days ago

Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}")

Categories

(Remote Protocol :: Marionette, defect, P5)

defect

Tracking

(firefox105 unaffected, firefox106 affected)

Tracking Status
firefox105 --- unaffected
firefox106 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in WebDriver:NewWindow → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in WebDriver:NewWindow)
Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in WebDriver:NewWindow) → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in POST /session/60e0eed8-f045-4acc-ab0f-7363ef74d82d/window/new {"type": "tab"})
Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in POST /session/60e0eed8-f045-4acc-ab0f-7363ef74d82d/window/new {"type": "tab"}) → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}")
See Also: → 1791102
See Also: → 1791111

This problem spiked late last week and especially all around debug builds. I assume the move for the Android test jobs from AWS to GCP is the factor here. And it's most likely also related to the other bugs as filed over the weekend and linked under see also.

I'll have to investigate.

Flags: needinfo?(hskupin)
See Also: → 1780219
Flags: needinfo?(hskupin)
Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}") → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (TEST-INFO took 80003ms)
Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (TEST-INFO took 80003ms) → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}")

Most of the failures as listed for this bug are actually coming from bug 1791111.

Depends on: 1791111

Interestingly the failures for this bug dropped a lot since the Android jobs moved from AWS to GCP. First I thought bug 1791111 might have shadowed it but that one was for debug builds only - and this bug is opt only.

I'll keep this bug open until next Monday and if no more failures get classified I will close it.

There are no more failures for this particular bug; the one as listed by the intermittent failure bot was wrongly classified. As said it looks like this failure is gone.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

Reopening the bug given that it still seems to happen (here for beta) even very very infrequently:
https://treeherder.mozilla.org/logviewer?job_id=393397753&repo=mozilla-beta&lineNumber=19972

Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

(In reply to Intermittent Failures Robot from comment #15)

  • windows10-32-2004-qr: 1
  • linux1804-64-qr: 2

Note that all these 3 test failures have been wrongly classified. I've corrected that.

The severity field for this bug is set to S4. However, the following bug duplicate has higher severity:

:whimboo, could you consider increasing the severity of this bug to S3?

For more information, please visit auto_nag documentation.

Flags: needinfo?(hskupin)

This is a failing test where we keep the default of S4. A new bug might be filed for a fix if needed, but right now the failure doesn't happen in such a frequency that we will work on it.

Flags: needinfo?(hskupin)

All the recently added Android debug-isolated-process failures are actually related to bug 1804027. Sheriffs could you please fix the classifications? Thanks.

Flags: needinfo?(sheriffs)

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #23)

All the recently added Android debug-isolated-process failures are actually related to bug 1804027. Sheriffs could you please fix the classifications? Thanks.

yes, will reclassify

Flags: needinfo?(sheriffs)

(In reply to Sandor Molnar from comment #24)

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #23)

All the recently added Android debug-isolated-process failures are actually related to bug 1804027. Sheriffs could you please fix the classifications? Thanks.

yes, will reclassify

Sandor, the opt jobs should not have been re-classified! These all belong to this particular bug.

Flags: needinfo?(smolnar)

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #25)

(In reply to Sandor Molnar from comment #24)

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #23)

All the recently added Android debug-isolated-process failures are actually related to bug 1804027. Sheriffs could you please fix the classifications? Thanks.

yes, will reclassify

Sandor, the opt jobs should not have been re-classified! These all belong to this particular bug.

I understand, will fix it.

Flags: needinfo?(smolnar)
Duplicate of this bug: 1811243

This failure is actually only happening on beta and beta sim on try. As such I'm kinda sure it has the same underlying issue as bug 1804027.

Depends on: 1804027
Moving bug to Remote Protocol::Marionette component per bug 1815831.
Component: geckodriver → Marionette
Product: Testing → Remote Protocol
Duplicate of this bug: 1830257

It seems to fail also on Windows, as it can be seen here ( and here is the log).

Summary: Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}") → Intermittent Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}")

(In reply to Serban Stanca [:SerbanS] from comment #58)

It seems to fail also on Windows, as it can be seen here ( and here is the log).

Not sure why you think that this failure is related to this bug. Nothing in that log shows something about /window/new for the type tab. What you see here is basically a hang in browsingContext.navigate which is covered by bug 1760291. I've already re-classified the failure.

Status: REOPENED → NEW
Summary: Intermittent Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}") → Intermittent Android Wd TEST-UNEXPECTED-TIMEOUT | expected OK (hang in "POST /session/%id/window/new {"type": "tab"}")
No longer blocks: 1825501
Depends on: 1825501

This should potentially be fixed by my patch on bug 1891008 for GeckoView.

Depends on: 1891008
You need to log in before you can comment on or make changes to this bug.