Closed Bug 1890553 Opened 10 months ago Closed 10 months ago

try selection of firefox-android nightly/beta tasks requires shippable builds -- not available for artifact builds

Categories

(Release Engineering :: General, defect, P2)

Tracking

(firefox127 fixed)

RESOLVED FIXED
Tracking Status
firefox127 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

geckoview shippable artifact builds fail on try.
Many firefox-android nightly/beta tasks rely on geckoview shippable builds.
bdk reports selecting A-C/focus/fenix tasks in try fuzzy, resulting in:
https://treeherder.mozilla.org/jobs?repo=try&revision=d18af45ab303ed41151c089b932d05a10c7925fc

Can we provide a better experience?

Could nightly/beta tasks that rely on shippable be removed from try fuzzy --artifact's task list?

How does this compare with the desktop experience?

For example, fenix-nightly (and focus-nightly) AAB builds rely on shippable geckoview; if those AAB builds are selected from mach try fuzzy --artifact, then shippable geckoview artifact builds are scheduled but fail:
https://treeherder.mozilla.org/jobs?repo=try&revision=cd397eee077a4ed54bab948dfd907998a5163c39

Everything works out fine with --no-artifact:
https://treeherder.mozilla.org/jobs?repo=try&revision=5af3c841e1e08a8d360c3fd2d8aa7da5d1843352

Or even faster with --no-artifact --disable-pgo:
https://treeherder.mozilla.org/jobs?repo=try&revision=603a6db9f10098fa1b6ba62e5f357530b29b7f59

(In reply to Geoff Brown [:gbrown] (pto Apr 11-18) from comment #0)

How does this compare with the desktop experience?

I was thinking of, for instance, desktop cppunit tests, which fail against artifact builds. You can run mach try fuzzy --artifact and select cppunit tests ... and they fail: https://treeherder.mozilla.org/jobs?repo=try&revision=9a79a3f1f1285e33c633fd45d3c40ea36273c768 . So that's a very similar experience, and similarly frustrating.

Could we / should we automatically schedule non-artifact builds for test tasks known to fail against artifact builds, even when artifact builds are requested of mach try?

Or, could we / should we remove such test tasks from the fuzzy/chooser task lists when artifact builds are requested?

Or, could we / should we warn about these conflicts?

:ahal - I am interested in your perspective.

Flags: needinfo?(ahal)

Lot's of pre-existing bugs / conversations on this :). Added a bunch of bugs to see also.

Though unlike those other cases, in this case the build doesn't work at all with artifact builds. So I think the correct solution here is to exclude these builds in the use_artifacts transform here:
https://searchfox.org/mozilla-central/rev/058ab60e5020d7c5c98cf82d298aa84626e0cd79/taskcluster/gecko_taskgraph/transforms/build.py#136

Flags: needinfo?(ahal)
See Also: → 1392613, 1384711, 1489128, 1751059
Assignee: nobody → gbrown
Priority: -- → P2
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a7cf9f29a4bf Do not try to use artifact builds for android shippable r=taskgraph-reviewers,jcristau
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: