Opened 6 months ago
Closed 3 months ago
#69668 closed defect (fixed)
Use matched Xcode / CLT versions on macOS 13 and macOS 14 GitHub Actions runners
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | admin@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | server/hosting | Version: | |
| Keywords: | Cc: | Dave-Allured (Dave Allured) | |
| Port: |
Description
On the macOS 14 GitHub Actions runner building MacPorts base it says:
checking Xcode location... /Applications/Xcode_15.0.1.app/Contents/Developer
Warning: The installed version of Xcode (15.0.1) is known to cause problems. Version 15.1 or later is recommended on macOS 14.
When building a port it says:
DEBUG: Xcode 15.0.1, CLT 15.3.0.0.1.1708646388
Can we switch to a newer Xcode?
Change History (7)
comment:1 Changed 6 months ago by jmroot (Joshua Root)
comment:2 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Each GitHub Actions runner has several versions of Xcode preinstalled. The macOS 14 runner has Xcode 14.3.1, 15.0.1, 15.1, 15.2, and 15.3 installed.
comment:3 Changed 6 months ago by jmroot (Joshua Root)
Hm, strange that they default to such an old version then. Yes, I'm sure we can run xcode-select.
comment:4 Changed 5 months ago by Dave-Allured (Dave Allured)
| Cc: | Dave-Allured added |
|---|
comment:5 Changed 4 months ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | Use newer Xcode on macOS 14 GitHub Actions runner → Use matched Xcode / CLT versions on macOS 13 and macOS 14 GitHub Actions runners |
|---|
Similarly, the macOS 13 GitHub Actions runner has:
DEBUG: Xcode 15.0.1, CLT 14.3.1.0.1.1683849156
This mismatch causes build failures due to a MacPorts base bug in compiler selection; see #70143.
comment:6 Changed 3 months ago by jmroot (Joshua Root)
comment:7 Changed 3 months ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Not without spending the significant time it would take to download and install it at the start of every CI run. Probably the best we can do is ask GitHub to update the version in the image.