Repository navigation
ci: fix Qt build - #119
Merged
Merged
ci: fix Qt build#119
Conversation
SetZero
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Windows test job printed "qt6ui skipped: Qt MinGW kit not found" twice per run: clippy and the unit tests compile
mumble-tauri, whosebuild.rsprobes for the Qt MinGW kit to build the minimal client, and a runner has none. The build job already setsSKIP_QT6UIfor this reason; the test job now does too. The minimal client is built and packaged by its own job, so nothing changes in what is produced.