macOS 11 artifact jobs require full shippable build despite artifacts being available
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: Gijs, Unassigned)
References
Details
Attachments
(1 file)
STR:
- clean central tree
- run
./mach try fuzzy --artifact --fulland select some macOS 11 mochitest-browser-chrome jobs - push: https://treeherder.mozilla.org/jobs?repo=try&revision=274324dfb2722a67bfe8944b259a0b7cf57a458f
ER:
artifact builds because I pushed with --artifact
AR:
no artifact builds.
This wastes resources as well as developer time, because the results take much longer to appear.
| Reporter | ||
Comment 1•4 years ago
|
||
Apparently we made artifact builds work locally in bug 1690870.
Comment 2•2 years ago
|
||
Looks like test-platforms.yml defines macosx1100-64-qr/debug which only runs jittests, and macosx1100-64-shippable-qr/opt which uses shippable builds. Can we add a plain opt platform, or add non-jittests to the debug one?
Comment 3•2 years ago
|
||
I don't see any downsides, but I'm waiting for Joel to get back to redirect the needinfo to him and confirm.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
I assume we can run on the opt instead of shippable, that should solve this problem.
Comment 5•2 years ago
|
||
I don't think this is as simple as using opt vs shippable, nor is it as simple as telling the task to use an artifact.
:sheehan, do you know how to get a build to use artifacts?
Updated•1 year ago
|
Comment 6•1 year ago
|
||
- package tests for build-macosx64-shippable/opt
- add macosx64-x64-opt and macosx64-aarch64-opt to the list of artifact jobs
Updated•1 year ago
|
Description
•