Status

defect
RESOLVED WONTFIX
3 years ago
a year ago

People

(Reporter: gps, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
We are currently building OS X on 10.7. As of Firefox 49, we no longer support OS X 10.6-10.8. We shouldn't be building OS X on an unsupported target platform. All OS X jobs should move to 10.9+.

This matters for the build system because we have to generate binaries that run on the host. As long as the builders in automation are OS X 10.7, we need to target OS X 10.7 for those binaries. Although we could probably target different OS X versions for host versus target binaries.

This bug might be WONTFIX if we ever cross-compile OS X builds from Linux. I'm not sure what the state of that is.
We're going to stay on 10.7 until we move to cross compiling on taskcluster in AWS.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
We're currently running cross-compiled debug builds in Taskcluster, but aren't running tests on them yet. We have 64-bit-only opt builds running, but not universal opt builds yet.
Selena tells me their target for switch-over is the end of Q3. That seems a long time to wait. :(
Blocks: 1255589

Comment 4

3 years ago
It is a product requirement that Firefox *not* run on MacOS 10.7. I don't know which host binaries we run as part of a build. Are all of our test machines running at least 10.9 now?
Blocks: 1255588

Updated

3 years ago
Flags: needinfo?(arich)
:bsmedberg: we will be severely reducing our 10.6 testing pool to only support ESR in the very near future (we just announced that we're stopping support, so it takes time to tear everything down). The rest of our OS X testing infrastructure is 10.10.
Flags: needinfo?(arich)
(Reporter)

Comment 6

3 years ago
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #4)
> It is a product requirement that Firefox *not* run on MacOS 10.7. I don't
> know which host binaries we run as part of a build. Are all of our test
> machines running at least 10.9 now?

In theory we could reconfigure the build system to use a separate OS X deployment target for host and target binaries. But I'd prefer we upgrade the builders themselves to OS X 10.9+, as this keeps the build configuration simple and is the ideal outcome (we shouldn't be using unsupported OS's in release automation).
(Reporter)

Comment 7

3 years ago
Since release automation is unable to move the OS X builders to 10.9+ and since it is a product requirement that Firefox not run on OS X <10.9, I guess that means we'll have to solve things in the build system.

I'll file a new bug.
Firefox 49 isn't shipping until September, so we still need to support 10.7 on the build farm for 46, 47 and 48 until then. We still need to support building for 10.7 for ESR45 until 2017. We can't upgrade the entire build pool to 10.9+ until ESR45 is EOL.
Or maintain a small number of 10.7 builders for older versions similar to how we're keeping some 10.6 test machines around until ESR45 goes EOL :)
(Reporter)

Updated

3 years ago
Blocks: 1270217
(In reply to Amy Rich [:arr] [:arich] from comment #1)
> We're going to stay on 10.7 until we move to cross compiling on taskcluster
> in AWS.

A year on, what's the status of this? Are we still unable to move to 10.9, or could this be reopened/fixed?
Flags: needinfo?(arich)
We switched the builds we ship to be cross-compiled from Linux in bug 927061, and bug 1324892 covers switching the SDK in use there to the 10.11 SDK (we can't use the 10.12 SDK yet, for reasons described in bug 1324892 comment 27 and bug 1324892 comment 29.
Flags: needinfo?(arich)
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.