You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 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.
Hm QtQml isn't used -- and there should be no dangling references to it. In Jamulus. It sounds like lreleasemay need it - but why only fail in 10% of cases?
🤖 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'".
Activity
ann0see commentedon Nov 8, 2026
Probably worth pushing it even further if possible.
[-]Migrate to macos-25 Github runner[/-][+]Migrate to macos-26 Github runner[/+]mcfnord commentedon Nov 14, 2026
🤖 AI: From 2026-09-15 to 2026-11-14,
Build for MacOS (artifacts)failed 11 times in 119autobuild.ymlruns, all 11 on #3646 (the Qt6 bump). All 11 are the samelreleasecrash, on Qt 6.11.2 and 6.12.0:dyld: Library not loaded: @rpath/QtQml.framework.mac.shinstalls onlyqtbase qttools qttranslations. On Linux with the same aqtinstall 3.3.0, 6.12.0'slreleasefails to loadlibQt6Qml.so.6withoutqtdeclarativeand runs with it; 6.10.2's runs either way. The failures come from the Qt version, not from themacos-15runner.pljones commentedon Nov 14, 2026
Hm
QtQmlisn't used -- and there should be no dangling references to it. In Jamulus. It sounds likelreleasemay need it - but why only fail in 10% of cases?mcfnord commentedon Nov 14, 2026
🤖 AI: The 10% is a mix of branches. The 11 failures are every completed macOS job on #3646 (11 of 11, plus 1 cancelled).
mainbuilds macOS with Qt 6.10.2 (autobuild.ymlL229), and itslreleasedoes not load QtQml. #3646 moves that line to 6.12.0, whoselreleasedoes. Addingqtdeclarativeto the--archiveslist inmac.sh(one-line commit) on #3646's headcda856c6makes the macOS job pass on Qt 6.12.0 (run). The unchanged head fails atlreleasewith the QtQml error on the same day's runner (run). Windows fails in both, inaqt: "Failed to locate XML data for Qt version '6.12.0'".