Closed Bug 1184117 Opened 9 years ago Closed 9 years ago

Make Android 4.0 opt-in by default on Try

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: kmoir)

References

Details

Attachments

(2 files)

We're hitting bug 1182285 on Try pushes, which is confusing devs and wasting their time tracking down a failure that they don't own. Can we make Android 4.0 opt-in for those who really want it?
QA Contact: catlee → kmoir
Assignee: nobody → kmoir
QA Contact: kmoir → catlee
Attachment #8636057 - Flags: review?(bugspam.Callek)
Attachment #8636059 - Flags: review?(bugspam.Callek)
Attachment #8636057 - Flags: review?(bugspam.Callek) → review+
Attachment #8636059 - Flags: review?(bugspam.Callek) → review+
Attachment #8636057 - Flags: checked-in+
Comment on attachment 8636059 [details] [diff] [review]
bug1184117trychooser.patch

and deployed new trychooser
Attachment #8636059 - Flags: checked-in+
verified on treeherder
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
So, I've tried opting in to those Android 4.0 tests, but it does not seem to work. I've looked at the patches on this bug and I ticked the right checkbox on trychooser. Anyone here know if there's some extra step I'm missing?

Also, the href on the checkbox points at bug 184117, not this one.
Do you know what might be going on here? This is blocking investigation into a sec-crit bug.
Status: RESOLVED → REOPENED
Flags: needinfo?(kmoir)
Resolution: FIXED → ---
Flags: needinfo?(kmoir)
Attachment #8636057 - Flags: checked-in+ → checked-in-
Depends on: 1188611
Ok, found a workaround for my specific problem using mozci-trigger:

mozci-trigger --revision <pre-existing try push revision> --buildername='Android 4.0 armv7 API 11+ try debug test mochitest-5'
Comment on attachment 8636057 [details] [diff] [review]
bug1184117bb-configs.patch

mozci fixed the problem :-)
Attachment #8636057 - Flags: checked-in- → checked-in+
I've re-landed the changes, the tests will be disabled by default on try again with the next reconfig
Verified that this is indeed disabled again on try
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: