Closed Bug 1004657 Opened 10 years ago Closed 10 years ago

Intermittent Android 4.0 NOT-robocop shutdown timeout

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 924622

People

(Reporter: emorley, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure)

Breaking out the Android panda instances from bug 918759.

eg:

(In reply to TBPL Robot from comment #2789)
> philor
> https://tbpl.mozilla.org/php/getParsedLog.php?id=38749817&tree=Fx-Team
> Android 4.0 Panda fx-team opt test robocop-5 on 2014-04-29 16:11:17
> revision: 3e0ff6c29303
> slave: panda-0613
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> Return code: 2

(In reply to TBPL Robot from comment #2803)
> KWierso
> https://tbpl.mozilla.org/php/getParsedLog.php?id=38842594&tree=B2g-Inbound
> Android 4.0 Panda b2g-inbound opt test plain-reftest-7 on 2014-04-30 17:59:28
> revision: aed338f33904
> slave: panda-0034
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> Return code: 2

(In reply to TBPL Robot from comment #2805)
> philor
> https://tbpl.mozilla.org/php/getParsedLog.php?id=38852462&tree=Mozilla-
> Inbound
> Android 4.0 Panda mozilla-inbound opt test robocop-5 on 2014-04-30 21:00:15
> revision: 658330efb152
> slave: panda-0519
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> Return code: 2

(In reply to TBPL Robot from comment #2807)
> edmorley
> https://tbpl.mozilla.org/php/getParsedLog.php?id=38861350&tree=Mozilla-
> Inbound
> Android 4.0 Panda mozilla-inbound opt test plain-reftest-2 on 2014-05-01
> 01:31:21
> revision: 293ecda82136
> slave: panda-0637
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> Return code: 2

(In reply to TBPL Robot from comment #2808)
> edmorley
> https://tbpl.mozilla.org/php/getParsedLog.php?id=38868538&tree=Fx-Team
> Android 4.0 Panda fx-team opt test plain-reftest-5 on 2014-05-01 04:59:18
> revision: 4cc15c7ea4d8
> slave: panda-0363
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> Return code: 2

Geoff - don't suppose you could take a look at the logs and see if anything leaps out? I've had a glance but I really struggle to see past the usual logcat noise (we seem to have several errors that occur in normal runs). Thank you :-)
Flags: needinfo?(gbrown)
Blocks: 1004668
(In reply to Ed Morley (Away until 6th May) [:edmorley UTC+0] from comment #0)
> Geoff - don't suppose you could take a look at the logs and see if anything
> leaps out? I've had a glance but I really struggle to see past the usual
> logcat noise (we seem to have several errors that occur in normal runs).
> Thank you :-)

Ed -- It feels like there are a lot of Android shutdown failures currently. Nothing much stands out in the logs. I'm checking into the robocop-5 case in bug 1004668 and will circle back here when I can. (But I wouldn't mind if someone else were to take this bug in the meantime!)
Flags: needinfo?(gbrown)
Summary: Intermittent Android 4.0 TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output → Intermittent Android 4.0 *NOT-robocop* TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output
(In reply to Geoff Brown [:gbrown] (PTO May 14 - May 21) from comment #16)
> Ed -- It feels like there are a lot of Android shutdown failures currently.
> Nothing much stands out in the logs. I'm checking into the robocop-5 case in
> bug 1004668 and will circle back here when I can. (But I wouldn't mind if
> someone else were to take this bug in the meantime!)

Thank you for taking a look anyway :-)
:snorp -- I'm noticing more and more intermittent Android test failures on shutdown, mostly hangs, but some crashes too. In addition to this bug, consider:

 - bug 984555 - shutdown crashes following Android 4.0 reftests
 - bug 959804 - same thing for Talos?
 - bug 1008014 - another Android 4.0 reftest shutdown crash
 - bug 986738 - shutdown crash following apparent hang on Android 2.3 robocop
 - bug 1004668 - hang following testUITelemetry on Android 4.0
 - bug 993813 - cannot kill fennec following testUITelemetry on Android 2.2
 - bug 1007824 - crash/hang following testANRReporter

I hope some of these have a common cause!

Can you have a look?
Flags: needinfo?(snorp)
(In reply to Geoff Brown [:gbrown] from comment #44)
> :snorp -- I'm noticing more and more intermittent Android test failures on
> shutdown, mostly hangs, but some crashes too. In addition to this bug,
> consider:

The fix for bug 924622 appears to have resolved the worst of the Android shutdown problems, including this bug (comment 109 and comment 110 are mis-filed / not Android 4.0).

Bug 1008422 is the only remaining frequent Android shutdown bug that I am aware of.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(snorp)
Resolution: --- → DUPLICATE
(Tweaking summary to avoid future TBPL false positives, now this is fixed)
Summary: Intermittent Android 4.0 *NOT-robocop* TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output → Intermittent Android 4.0 NOT-robocop shutdown timeout
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.