Open Bug 1491465 Opened 7 years ago Updated 3 years ago

Periodically run a build with the most recent rustc nightly

Categories

(Firefox Build System :: General, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: chmanchester, Unassigned)

References

Details

We want to know if there's bustage generally, and in particular for the Tup build, where we're suggesting people run `rustup install nightly` and using that as their toolchain for the build.
Triaging Chris, are you going planning to take on this work or is this something Mike will look at?
Flags: needinfo?(cmanchester)
I'm looking into this, although based on looking into it so far it may prove to be more trouble than it's worth to automate. Either way I'll update things here.
Assignee: nobody → cmanchester
Flags: needinfo?(cmanchester)
My idea for this was to have a cron task that runs once a day and does a set of builds (maybe just Tup and linux) with the nightly rustc and send out a notification if things fail. This looks like it will take significant task graph hacking and/or maintenance of task definitions to achieve, although I think I have a handle on the basic idea, which would be to have a nightly-rustc task that specifies "never" as its optimization strategy and a "nightly-rustc-build" kind that specifies a set of builds that will rely on this rust toolchain. This last part seems bad, because we're going to end up repeating the regular task definitions verbatim (ideally they wont differ at all aside from the toolchain), but the only analogous things I've found are artifact builds and static analysis builds, and these both take the approach of repeating task definitions with certain parameters tweaked. What I'd like is a kind that takes regular build tasks and replaces their toolchain dependencies. Any pointers in that direction from someone who understands the taskgraph code better than I do would be much appreciated.
With :kmoir's consent, I'm reviewing the backlog for bugs in FFx Build System to see if we can do some things to clean up the backlog. This bug appears to be an enhancement or feature request. If so, please set the bug's severity to `enhancement` and/or add the `feature` keyword depending on if this is an improvement to an existing thing, or a new feature/tool/system.
Flags: needinfo?(cmanchester)
Severity: normal → enhancement
Flags: needinfo?(cmanchester)

I wasn't able to make progress here. The discussion in bug 1614858 is relevant to this though, I think there may be a close-to-shared solution there.

Assignee: cmanchester → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.