1287455 - Intermittent mobile/android/tests/browser/chrome/test_session_scroll_position.html | application ran for longer than allowed maximum time

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Testing, defect)

Description

[Treeherder Bug Filer]

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

Comment 1

[Geoff Brown [:gbrown]]

"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.

Comment 2

[Geoff Brown [:gbrown]]

Over the weekend we increased android m-c tests signficantly:

mochitest-chrome: 3932/0/5
mochitest-chrome: 5050/0/5

Comment 3

[Geoff Brown [:gbrown]]

https://hg.mozilla.org/integration/autoland/rev/20a6fd076505809220e031dd594e03029459a664 added the new tests.

Comment 4

[Geoff Brown [:gbrown]]

:gerard-majax is going to try skipping the new tests on Android.

Comment 5

[:gerard-majax]

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

[:gerard-majax]

try for reference: https://treeherder.mozilla.org/#/jobs?repo=try&revision=fee232e6cad5

Comment 7

[:gerard-majax]

Attachment: Skip tests that are not useful on Android r?

Comment 8

[:gerard-majax]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=6646f3d27f9e

Comment 9

[:gerard-majax]

So checking those results is being blocked by bug 1287501.

Comment 10

[William Lachance (:wlach)]

(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

[:gerard-majax]

(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

[:gerard-majax]

Hm I just discovered bug 1286942

Comment 13

[:gerard-majax]

So browser elements chrome tests are taking long ; that might explain everything. Sadly, tests triggered four hours ago have started a few minutes ago.

Comment 14

[Geoff Brown [:gbrown]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=09685eafeece - with dom/browser-element skipped

Comment 15

[:gerard-majax]

https://treeherder.allizom.org/#/jobs?repo=try&revision=4c153cc57efb

Comment 16

[:gerard-majax]

Attachment: Skip tests that are not useful on Android r?

Comment 17

[:gerard-majax]

(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

[:gerard-majax]

Attachment: Bug 1287455 - Skip tests that are not useful on Android

Review commit: https://reviewboard.mozilla.org/r/65166/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/65166/

Comment 19

[:gerard-majax]

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

[Kan-Ru Chen [:kanru] (UTC+9)]

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.

Comment 21

[:gerard-majax]

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

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0f83a2cbea68
Skip tests that are not useful on Android r=kanru

Comment 23

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/0f83a2cbea68

Comment 28

[Intermittent Failures Robot]

10 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 5
* fx-team: 2
* try: 1
* mozilla-central: 1
* autoland: 1

Platform breakdown:
* android-4-3-armv7-api15: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1287455&startday=2016-07-18&endday=2016-07-24&tree=all