unnecessary full macOS build when requesting --artifact
Categories
(Thunderbird :: Build Config, defect)
Tracking
(Not tracked)
People
(Reporter: KaiE, Unassigned)
Details
When requesting a try build with syntax
try: -b o -p win64,linux64,macosx64 -u none --artifact
in addition to a macOS Ba, a regular full B build is started.
Intentional or bug? Should the B build be suppressed?
For example:
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=435783ede368d7e6bce4df53a40549bc40a88da6
|
||
Comment 1•4 years ago
|
||
What happens if you explicitly ask for macosx64-shippable rather than macosx?
Because there's a limited pool of macs to run tests, macOS Try and Try-c-c builds are either debug or shippable. No regular optimized builds.
|
||
Comment 2•4 years ago
|
||
I think this is the code that causes it:
https://searchfox.org/mozilla-central/rev/36fd1ef40463be6a9ec615ad0c435d4afeb56b88/taskcluster/taskgraph/try_option_syntax.py#343
I don't think you can get around it while using try syntax. I use a task config file for various reasons, which doesn't have the same problem, but is a bit of a pain.
|
|
||
Comment 3•3 years ago
|
||
This looks like it got fixed somewhere along the way, probably by bug 1695072.
Description
•