1287720 - re-enable dom/browser-element/mochitest/chrome.ini

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Testing, defect, P2)

Description

[:gerard-majax]

In bug 1287455 we disabled them because it was taking too long to run the mochitest-chrome test suite

Comment 1

[Geoff Brown [:gbrown]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=3d0bbd4ed111 looks okay. There is now plenty of time on taskcluster; on buildbot-based opt, mochitest-chrome is running long, but not quite timing out. Let's give that a try.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f0d2679582be
Enable dom/browser-element mochitest-chrome tests on Android; r=me

Comment 3

[Geoff Brown [:gbrown]]

Backed out with https://hg.mozilla.org/integration/mozilla-inbound/rev/5083d26c9c92a364f954be87a4aea2323950afc4 for causing failures like http://archive.mozilla.org/pub/mobile/tinderbox-builds/mozilla-inbound-android-api-15/1469638277/mozilla-inbound_ubuntu64_vm_armv7_mobile_test-mochitest-chrome-bm51-tests1-linux64-build73.txt.gz - intermittent application timeouts in buildbot Android 4.3 opt mochitest-chrome.

We could land a buildbot patch to increase the number of mochitest-chrome chunks, but that would not be simple because the mozharness configs on aurora, beta, etc would also need to be updated.

I think I would prefer to wait until the buildbot Android tests are retired, then simply re-land the manifest patch. (If enabling these tests is urgent, needinfo me.)

Comment 4

[Geoff Brown [:gbrown]]

Buildbot Android tests were recently retired; these should be fine on taskcluster.

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

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c60c180ba26b
Enable dom/browser-element mochitest-chrome tests on Android; r=me

Comment 6

[Phil Ringnalda (:philor)]

https://hg.mozilla.org/mozilla-central/rev/c60c180ba26b