This bug is to help us track it from Release Engineering's side.
Assignee: nobody → armenzg
Depends on: 961284
== Old status from February == * Waiting to green things up ** https://bugzilla.mozilla.org/show_bug.cgi?id=967704#c16 ** https://tbpl.mozilla.org/?tree=Ash&jobname=Android%202.3
See status in here: https://bugzilla.mozilla.org/show_bug.cgi?id=967704#c30
5 years ago
Assignee: armenzg → kmoir
:gbrown now that there are a lot of 2.3 tests running on emulators are there any tests on Tegras that we can start to disable?
Yes, I think so! Let's keep these caveats in mind: 1. Android 2.3 armv6 tests are not running yet 2. Android 2.3 Opt tests do not run yet on Aurora, Beta, etc (we are riding the trains) 3. We do not and will not attempt to run Talos tests on Android 2.3 4. Some tests are disabled on Android 2.3, as tracked in bug 979921, notably: - about one third of the robocop tests are skipped - many media mochitests are skipped: content/media/test/*, content/media/webaudio/test/*, dom/media/tests/mochitest/* I think we can stop running all "Android 2.2 Opt" tests (including Talos) on trunk now. :blassey -- What do you think?
Flags: needinfo?(gbrown) → needinfo?(blassey.bugs)
#4 concerns me, since the two areas you call out (UI and media) are things that can be different between android versions. I've emailed mobile developers to see if we can make a push on fixing up those robocop tests. Need-info'ing Maire to see her comfort for running without these media tests on 2.x. What we can do now is shut down the rest of them, but keep robocop and media mochitests running on 2.2.
Flags: needinfo?(blassey.bugs) → needinfo?(mreavy)
Okay so I'll write a patch to do the following -change should ride the trains -leave robocop and media mochitests running on 2.2 (media mochitests correspond to M2-M4) -all other 2.2 opt tests should be disabled including talos on trunk Sound good?
Yes, that sounds good.
Okay thanks, I've opened bug 1017599 to track disabling the tests
There are significant differences between 2.2 and 2.3, so I'm very uncomfortable not testing 2.3 if it is still a product/platform we care about.
(In reply to Maire Reavy [:mreavy] (Please needinfo me) from comment #9) > There are significant differences between 2.2 and 2.3, so I'm very > uncomfortable not testing 2.3 if it is still a product/platform we care > about. To be clear, we're bringing up 2.3 testing and shutting down 2.2 testing (in conjunction with EOL'ing 2.2). right now, many media related tests don't pass on 2.3, so they're disabled. The question is if we feel comfortable with only testing media stuff on 4.0. If you're not comfortable with that, you'll need to the tests fixed on 2.3 ASAP.
Sorry for my late reply. I saw the needinfo (thanks!), but I didn't realize this was blocked on me. Thanks for the pointers to the bugs, Geoff. I think for now we should disable them, but use the existing bugs to investigate the failures -- at least to a certain point. It looks like JW is actively looking at resolving the failures on bug 981898 for Android 2.3. I also can ask him to take a look at bug 981889. JW has been an active contributor to web audio over the past year. For Bug 981881, I love to ask gcp to take a day to investigate (ideally within the next 2-3 weeks)and assess how much work it would be to resolve the webrtc failures on that bug. They all appear to have the same root cause. If the work required on each bug isn't more than a few days each, we should fix them because there are enough differences between 2.3 and 4.x that it's worth that effort for peace of mind.
I think this can be closed now. We do run 2.3 tests on Emulators on EC2. We may need to shift around the instance types that we use for them but the substantial work is done here. See bug 1024091 for details.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.