Closed
Bug 1269063
Opened 9 years ago
Closed 9 years ago
Long running Android reftest failures no longer report "application ran for longer than allowed maximum time"
Categories
(Testing :: General, defect)
Testing
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: gbrown, Assigned: gbrown)
Details
Android 4.3 opt reftest-16 is frequently failing after 75 minutes (the current max job time), but logs do not show the regular message "application ran for longer than allowed maximum time".
http://hg.mozilla.org/mozilla-central/annotate/2b7c421063ad/build/mobile/remoteautomation.py#l120
http://archive.mozilla.org/pub/mobile/tinderbox-builds/fx-team-android-api-15/1461760075/fx-team_ubuntu64_vm_armv7_large_test-plain-reftest-16-bm121-tests1-linux64-build2.txt.gz
http://archive.mozilla.org/pub/mobile/tinderbox-builds/fx-team-android-api-15/1461766114/fx-team_ubuntu64_vm_armv7_large_test-plain-reftest-16-bm131-tests1-linux64-build13.txt.gz
![]() |
Assignee | |
Comment 1•9 years ago
|
||
The Android max job time is currently 5400 seconds = 90 minutes. So it looks like the job time is unrelated to these failures, which look more and more like regular exceptions that just happen to occur 70 to 80 minutes into opt R16.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•