650686 - [tracking] Android browser-chrome permaoranges

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Phil Ringnalda (:philor)]

Yes, it is sort of an abuse of tracking bugs to use one just because you want to have a single bug number to use to star "yes, this is the same 23 failures as the last time," but then I've never really seen a non-abusive tracking bug, and at least this one has a set lifespan, and someone who's going to close it at the end of that.

Comment 1

[Phil Ringnalda (:philor)]

Attachment: disable the Android permaorange

Along with the patch from bug 651554, this will get Android b-c down to just the recent regressions, autocomplete from bug 636792, appmenu and find from bug 612193, and bug 658941's awesomescreen and contentpopup from bug 657997.

With those fixed, we'd be down to a browser_navigation.js timeout and the shutdown crash on desktop Linux, and green on Android and Maemo, at which point we ought to be able to stop missing regressions for days at a time, and we can switch TraceMonkey to testing Android instead of the odd-but-stable choice of Maemo Qt.

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

Comment on attachment 535972 [details] [diff] [review]
disable the Android permaorange

Sad, but necessary I guess. At least we have some testing on desktop and maemo.

Comment 3

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Pushed the temporary disabling : http://hg.mozilla.org/mozilla-central/rev/d0583d604249

Comment 4

[Phil Ringnalda (:philor)]

And since the remaining permaoranges are just fresh regressions that are being dealt with, I'm declaring victory here.