Closed
Bug 1411408
Opened 8 years ago
Closed 7 years ago
Remove macosx64 static analysis from try chooser
Categories
(Release Engineering :: General, enhancement, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwatt, Assigned: tjr)
References
Details
Attachments
(1 file)
I selected "machosx64 static analysis" using try chooser, and the result is the failure I reported in bug 1411394.
Comment 1•8 years ago
|
||
That would be because bug 1355118 or bug 1208787, depending on how you look at it. On OS X, the regular builds do static analysis, so bug 1355118 removed them (without, because nobody ever does, removing them from trychooser).
Comment 2•8 years ago
|
||
So this bug should be about removing them from try chooser?
Comment 3•8 years ago
|
||
Yep, it's a trychooser bug about removing the "macosx64 static analysis" line in the Platforms section.
Updated•8 years ago
|
Severity: normal → minor
Priority: -- → P2
Summary: Try chooser produces an invalid task when using "machosx64 static analysys", causing Gecko Decision Task to fail → Remove macosx64 static analysis from try chooser
![]() |
Reporter | |
Comment 4•8 years ago
|
||
Why is this "minor"? This once again bit me and caused me to submit a Try job only to discover later it had been rejected by the Decision task. This is wasting my time.
Please point me to the trychooser source and I'll submit a patch. I found:
https://hg.mozilla.org/build/tools/file/tip/trychooser/index.html
but that says the code moved, but then there's no sign of the code at the github.com link it says it moved to.
Flags: needinfo?(catlee)
Comment 5•8 years ago
|
||
Code is here IIRC: https://github.com/mozilla-releng/services/tree/master/src/releng_frontend/src/static/trychooser
Flags: needinfo?(catlee)
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Assignee: nobody → tom
Status: NEW → ASSIGNED
Updated•7 years ago
|
Attachment #8952659 -
Flags: review+
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•