Closed
Bug 964589
Opened 10 years ago
Closed 9 years ago
try -u all does not trigger Android x86 S4
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gbrown, Assigned: chmanchester)
References
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2956] )
Attachments
(2 files)
6.36 KB,
patch
|
gbrown
:
review+
|
Details | Diff | Splinter Review |
3.01 KB,
patch
|
armenzg
:
review+
|
Details | Diff | Splinter Review |
In https://tbpl.mozilla.org/?tree=Try&rev=1399e9c332d9, I specified: try: -b o -p linux64,android,android-x86,android-armv6 -u all -t all but no Android x86 tests were scheduled. I expected S4 to run. In contrast, try pushes seem to work fine for Android x86 if a particular test job is specified. For example, https://tbpl.mozilla.org/?tree=Try&rev=0431c24939d4 specified: try: -b o -p linux64,android,android-x86 -u mochitest-1,robocop-1,reftest,plain-reftest-1 -t none and Android x86 S4 ran, as I would expect.
Comment 2•10 years ago
|
||
This is only to bring trychooser up-to-date. It does not address the issue filed.
Attachment #8368672 -
Flags: review?(gbrown)
Comment 3•10 years ago
|
||
I should try to read bug 915870 to see how I worked on this.
Reporter | ||
Comment 4•10 years ago
|
||
Comment on attachment 8368672 [details] [diff] [review] trychooser.diff Review of attachment 8368672 [details] [diff] [review]: ----------------------------------------------------------------- BTW, I like the "only x86" info but I do not see much value to the "not x86" info.
Attachment #8368672 -
Flags: review?(gbrown) → review+
Updated•10 years ago
|
Assignee: armenzg → nobody
Comment 5•10 years ago
|
||
Once we realize just how incredibly sloppy we've gotten about enforcing the rather minimal visibility requirements, this bug is a very likely place that we'll start.
Comment 6•10 years ago
|
||
I'm working on the side something for bug 983802.
Comment 7•10 years ago
|
||
Pinged Armen in bug 983802.
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2946]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2946] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2951]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2951] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2956]
Comment 9•9 years ago
|
||
So, as stated in the dupe, I got backed out because of this. Is there a reason this doesn't run by default?
Assignee | ||
Comment 10•9 years ago
|
||
I've been backed out for this before, as well.
Attachment #8666104 -
Flags: review?(armenzg)
Updated•9 years ago
|
Attachment #8666104 -
Flags: review?(armenzg) → review+
Assignee | ||
Comment 11•9 years ago
|
||
http://hg.mozilla.org/build/buildbotcustom/rev/b7f3c09d04d1
Assignee | ||
Comment 12•9 years ago
|
||
I'm seeing S4 on some recent -u all runs, this is fixed.
Assignee: nobody → cmanchester
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•