Closed
Bug 1287455
Opened 8 years ago
Closed 8 years ago
Intermittent mobile/android/tests/browser/chrome/test_session_scroll_position.html | application ran for longer than allowed maximum time
Categories
(Firefox for Android Graveyard :: Testing, defect)
Firefox for Android Graveyard
Testing
Tracking
(firefox50 fixed)
RESOLVED
FIXED
Firefox 50
| Tracking | Status | |
|---|---|---|
| firefox50 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: gbrown)
References
Details
(Keywords: intermittent-failure)
Attachments
(1 file, 2 obsolete files)
Filed by: tomcat [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=649941&repo=autoland http://archive.mozilla.org/pub/mobile/tinderbox-builds/autoland-android-api-15-debug/1468828253/autoland_ubuntu64_vm_armv7_large-debug_test-mochitest-chrome-bm68-tests1-linux64-build3.txt.gz
|
Assignee | |
Comment 1•8 years ago
|
||
"application ran for longer than allowed maximum time" means the mochitest-chrome job is running for longer than expected -- nothing to do with this particular test. I'd probably file these as bug 1160010. Also affecting bug 1204281 and others. I wonder if we are running more tests.
Assignee: nobody → gbrown
|
|
Assignee | |
Comment 2•8 years ago
|
||
Over the weekend we increased android m-c tests signficantly: mochitest-chrome: 3932/0/5 mochitest-chrome: 5050/0/5
|
|
Assignee | |
Comment 3•8 years ago
|
||
https://hg.mozilla.org/integration/autoland/rev/20a6fd076505809220e031dd594e03029459a664 added the new tests.
|
|
Assignee | |
Comment 4•8 years ago
|
||
:gerard-majax is going to try skipping the new tests on Android.
Blocks: 1286530
|
||
Comment 5•8 years ago
|
||
dom/alarm/test/chrome.ini | 7 + dom/base/test/chrome.ini | 6 + dom/bindings/test/chrome.ini | 4 +- dom/browser-element/mochitest/chrome.ini | 91 ++++++- dom/browser-element/mochitest/priority/chrome.ini | 19 ++ dom/contacts/tests/chrome.ini | 48 +++- dom/html/test/chrome.ini | 8 +- dom/inputmethod/mochitest/chrome.ini | 52 ++++ dom/mobilemessage/tests/mochitest/chrome.ini | 2 + dom/network/tests/chrome.ini | 8 +- dom/power/test/chrome.ini | 9 + dom/presentation/tests/mochitest/chrome.ini | 12 +- dom/settings/tests/chrome.ini | 19 +- dom/tests/mochitest/general/chrome.ini | 2 + dom/tests/mochitest/geolocation/chrome.ini | 9 + dom/tests/mochitest/notification/chrome.ini | 8 + dom/tv/test/mochitest/chrome.ini | 19 ++
|
|
||
Comment 6•8 years ago
|
||
try for reference: https://treeherder.mozilla.org/#/jobs?repo=try&revision=fee232e6cad5
|
|
||
Comment 7•8 years ago
|
||
|
|
||
Comment 9•8 years ago
|
||
So checking those results is being blocked by bug 1287501.
|
||
Comment 10•8 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #9) > So checking those results is being blocked by bug 1287501. FWIW, you can look at your results on stage in cases like this: https://treeherder.allizom.org/#/jobs?repo=try&revision=6646f3d27f9e
|
|
||
Comment 11•8 years ago
|
||
(In reply to William Lachance (:wlach) from comment #10) > (In reply to Alexandre LISSY :gerard-majax from comment #9) > > So checking those results is being blocked by bug 1287501. > > FWIW, you can look at your results on stage in cases like this: > > https://treeherder.allizom.org/#/jobs?repo=try&revision=6646f3d27f9e And yet mochitest chrome jobs are not starting at all on both instances :/
|
|
||
Comment 12•8 years ago
|
||
Hm I just discovered bug 1286942
|
|
||
Comment 13•8 years ago
|
||
So browser elements chrome tests are taking long ; that might explain everything. Sadly, tests triggered four hours ago have started a few minutes ago.
|
|
Assignee | |
Comment 14•8 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=09685eafeece - with dom/browser-element skipped
|
|
||
Comment 16•8 years ago
|
||
|
|
||
Comment 17•8 years ago
|
||
(In reply to Geoff Brown [:gbrown] from comment #14) > https://treeherder.mozilla.org/#/jobs?repo=try&revision=09685eafeece - with > dom/browser-element skipped So I have checked on previous pushes and I see those tests in mochitest debug 3 and 4 on android 4.3, taking roughly the same amount of time. I am not sure we can that safely disable those.
|
|
||
Comment 18•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/65166/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/65166/
Attachment #8772334 -
Flags: review?(kchen)
|
|
||
Updated•8 years ago
|
Attachment #8772039 -
Attachment is obsolete: true
|
|
||
Updated•8 years ago
|
Attachment #8772288 -
Attachment is obsolete: true
|
|
||
Comment 19•8 years ago
|
||
Comment on attachment 8772334 [details] Bug 1287455 - Skip tests that are not useful on Android Review request updated; see interdiff: https://reviewboard.mozilla.org/r/65166/diff/1-2/
|
||
Comment 20•8 years ago
|
||
Comment on attachment 8772334 [details] Bug 1287455 - Skip tests that are not useful on Android https://reviewboard.mozilla.org/r/65166/#review62222 ::: dom/contacts/tests/chrome.ini:2 (Diff revision 2) > [DEFAULT] > - > +skip-if = toolkit == 'android' Here and below. Please add bug number and reason to skip the tests.
Attachment #8772334 -
Flags: review?(kchen) → review+
|
|
||
Comment 21•8 years ago
|
||
Comment on attachment 8772334 [details] Bug 1287455 - Skip tests that are not useful on Android Review request updated; see interdiff: https://reviewboard.mozilla.org/r/65166/diff/2-3/
|
||
Comment 22•8 years ago
|
||
Pushed by alissy@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0f83a2cbea68 Skip tests that are not useful on Android r=kanru
|
||
Comment 23•8 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/0f83a2cbea68
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 50
| Comment hidden (Intermittent Failures Robot) |
|
||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•