Skip to content

Migrate to macos-26 Github runner #3984

Open

Description

@pljones

What is the current behaviour and why should it be changed?

Current macOS builds run on Github runner macos-15. Determine whether the "main" build can run with macos-26 (leaving "legacy" alone (for now)).

Purpose: A number of branch and main builds have had their macos-15 runner builds fail recently. Moving to macos-26 may reduce the problem.

Describe possible approaches

  • Move all autobuild matrix entries from macos-15 to macos-26 in one go
    • Might save work if "it just works" but would be more open to risk of macOS legacy or iOS builds failing
  • Move all of them one at a time
    • Basically, this is the first one as it's most likely to work
    • Next would be the iOS one (probably equally likely to just work)
    • Doing legacy might mean dropping support for older macs.

Has this feature been discussed and generally agreed?

Briefly.

Activity

  1. added this to the Release 4.1.0 milestone on Nov 8, 2026
  2. ann0see commented on Nov 8, 2026

    @ann0see
    Member

    Probably worth pushing it even further if possible.

  3. changed the title [-]Migrate to macos-25 Github runner[/-] [+]Migrate to macos-26 Github runner[/+] on Nov 10, 2026
  4. mcfnord commented on Nov 14, 2026

    @mcfnord
    Contributor

    🤖 AI: From 2026-09-15 to 2026-11-14, Build for MacOS (artifacts) failed 11 times in 119 autobuild.yml runs, all 11 on #3646 (the Qt6 bump). All 11 are the same lrelease crash, on Qt 6.11.2 and 6.12.0: dyld: Library not loaded: @rpath/QtQml.framework. mac.sh installs only qtbase qttools qttranslations. On Linux with the same aqtinstall 3.3.0, 6.12.0's lrelease fails to load libQt6Qml.so.6 without qtdeclarative and runs with it; 6.10.2's runs either way. The failures come from the Qt version, not from the macos-15 runner.

  5. pljones commented on Nov 14, 2026

    @pljones
    CollaboratorAuthor

    Hm QtQml isn't used -- and there should be no dangling references to it. In Jamulus. It sounds like lrelease may need it - but why only fail in 10% of cases?

  6. mcfnord commented on Nov 14, 2026

    @mcfnord
    Contributor

    🤖 AI: The 10% is a mix of branches. The 11 failures are every completed macOS job on #3646 (11 of 11, plus 1 cancelled). main builds macOS with Qt 6.10.2 (autobuild.yml L229), and its lrelease does not load QtQml. #3646 moves that line to 6.12.0, whose lrelease does. Adding qtdeclarative to the --archives list in mac.sh (one-line commit) on #3646's head cda856c6 makes the macOS job pass on Qt 6.12.0 (run). The unchanged head fails at lrelease with the QtQml error on the same day's runner (run). Windows fails in both, in aqt: "Failed to locate XML data for Qt version '6.12.0'".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status
      Triage

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions