Enable GeckoView builds on Mac OS workers
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: owlish, Unassigned)
References
Details
The context for this ticket is the build currently being broken for mobile engineers who works on Macs. Three people are currently blocked by the issue. Fixing issues like this is not always simple because it takes a lot of time to identify the commit that broke the build and it's not always immediately clear who needs to fix it. For more details, see the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1729760
It would be great if we had a task that runs a mobile build on Mac OS (currently we only do Linux) in autoland, to prevent these sort of issues happen in the future.
|
||
Updated•3 years ago
|
|
|
||
Comment 1•3 years ago
|
||
Sorry, found this more complicated than I anticipated and haven't been finding time for it.
|
|
||
Comment 2•3 years ago
|
||
One issue that gave me pause here was deciding which build(s) to run on osx. We have many linux-hosted android build variants: arm7, aarch64, x86_64, opt vs debug, lite, etc. If we ran one variant on osx (build-android-x86_64/debug?), would that be sufficient, or will we just be back here in another month with a aarch64-only, osx-only, lite-only failure?
The bigger issue is that, aiui, all of our osx builds are cross-compiles running on linux hosts. I'm not aware of the history or reasons behind that: Why don't we run builds on osx? Would we need new toolchains to support osx-hosted android cross compiles?
:glandium - You probably have a much better idea of what's needed here. Can you share your thoughts?
|
||
Comment 3•3 years ago
|
||
We don't have a very large capacity to run native mac builds on automation. Apart from bug 1729760, was this broken recently? There's a balance between the amount of churn happening and the number of combinations we can run on automation. If it doesn't break often, I'd say we have the right amount of testing at the moment.
|
||
Comment 4•3 years ago
|
||
If the job only ran on mozilla-central by default with the ability for sheriffs to manually trigger on autoland in backfill situations, would that suffice?
|
||
Comment 5•3 years ago
|
||
It sounds like this is primarily for detecting/preventing local build bustage for developers who rely on geckoview, and who use a mac for development.
(In reply to Ryan VanderMeulen [:RyanVM] from comment #4)
If the job only ran on mozilla-central by default with the ability for sheriffs to manually trigger on autoland in backfill situations, would that suffice?
Probably, as long as sheriffs could detect bustage within a reasonable time window (backstops+backfills would probably work if we're concerned about load).
The main additional concern here is around who gets the build running manually, automates it on try pushes, then submits the patch for review to enable in production. It sounds like this will be in the top 5 releng mobile priorities for H1, but we can also help mentor a motivated non-releng developer if someone has cycles sooner.
Description
•