Closed Bug 1521195 Opened 5 years ago Closed 5 years ago

Android 7.0 x86 geckoview-junit perma-fail: TEST-UNEXPECTED-TIMEOUT | runjunit.py | Timed out after 2400 seconds in AccessibilityTest

Categories

(GeckoView :: General, defect, P1)

x86
Android
defect

Tracking

(firefox-esr60 wontfix, firefox65 wontfix, firefox66 wontfix, firefox67 affected)

RESOLVED DUPLICATE of bug 1553515
Tracking Status
firefox-esr60 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- affected

People

(Reporter: gbrown, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

+++ This bug was initially created as a clone of Bug #1510705 +++

+++ This bug was initially created as a clone of Bug #1506276 +++

Bug 1506276 and bug 1510705 addressed hangs in Android 7.0 x86 geckoview-junit tests, but the task continues to hang, failing with "Timed out after 2400 seconds".

Note that the geckoview-junit tests on Android 7.0 x86 are running as tier 3 tasks currently (because they keep failing): That means they are hidden by default and not sheriffed. Failures are not starred by sheriffs, so they don't show up in the intermittent-failures reports -- but they are happening on every push!

You can view the tasks on mozilla-central with:

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=android%2C7.%2C0%2Cgeckoview-junit

Examples:

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=222677758&repo=mozilla-central&lineNumber=1395

[task 2019-01-18T10:49:20.162Z] 10:49:20 INFO - TEST-START | org.mozilla.geckoview.test.AccessibilityTest.testTree
[task 2019-01-18T11:29:17.025Z] 11:29:17 WARNING - TEST-UNEXPECTED-TIMEOUT | runjunit.py | Timed out after 2400 seconds

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=222677625&repo=mozilla-central&lineNumber=1460

[task 2019-01-18T10:47:55.757Z] 10:47:55 INFO - TEST-START | org.mozilla.geckoview.test.AccessibilityTest.autoFill_navigation
[task 2019-01-18T11:27:52.418Z] 11:27:52 WARNING - TEST-UNEXPECTED-TIMEOUT | runjunit.py | Timed out after 2400 seconds

P1 for perma-fail test.

Priority: -- → P1
Assignee: nobody → mbrubeck
Status: NEW → ASSIGNED
Summary: Android 7.0 x86 geckoview-junit perma-fail: TEST-UNEXPECTED-TIMEOUT | runjunit.py | Timed out after 2400 seconds → Android 7.0 x86 geckoview-junit perma-fail: TEST-UNEXPECTED-TIMEOUT | runjunit.py | Timed out after 2400 seconds in AccessibilityTest

Is this junit test timeout a dupe of bug 1482231?

This timeout affects both Android x86 and x86_64.

I think it is best to keep bug 1482231 as a place to report the infrequent intermittent timeouts seen on Android 4.3, and sort out the Android 7.0 perma-fail here. There's a chance they will turn out to have the same underlying cause, but if not there is certainly a difference in importance/urgency: we really need this bug fixed, but can live with the other one.

No longer blocks: 1503299

Resolving as WFM because there have no reported failures in the last five weeks.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

There have been no more failures because geckoview-junit is no longer running on Android 7.0 -- it was turned off because it was perma-fail, with failures like this one!

(In reply to Geoff Brown [:gbrown] from comment #9)

There have been no more failures because geckoview-junit is no longer running on Android 7.0 -- it was turned off because it was perma-fail, with failures like this one!

Oh! Should I reopen all these bugs I just closed? I now see we stopped running the geckoview-junit tests on Android 7.0 x86_64 (bug 1525738) back in February and that we're only running them on the Android 4.3 (arm7) emulator.

Flags: needinfo?(gbrown)

I think most of the other bugs you closed were Android 4.3 bugs, so it was good to close them.

Let's just re-open this one.

Here's a recent failure from a try push:

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=237686855&repo=try&lineNumber=1744

While we're here, :mbrubeck, any news?

Status: RESOLVED → REOPENED
Flags: needinfo?(gbrown) → needinfo?(mbrubeck)
Resolution: WORKSFORME → ---
Flags: needinfo?(mbrubeck)
Assignee: mbrubeck → nobody

This was fixed in Bug 1553515.

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.