[CI] Enhance CI run and make mac ci less likely to fail #7561
Conversation
This file contains 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
|
did set up the homebrew way of build according to the ci description in #7564 (comment) in a osx virtual machine (mojave, sdk 10.14) and darktable-3.4.x branch was built fine ... |
|
Yeah. That's why I needed to make a workaround for gh actions - this is workaround + beefing up ;) |
|
@johnny-bit : the windows failures are transients or really something to look at ? Some packages not updated... |
According to msys2 folks - "sync issues on mirrors, usually gone in 15-30 mins, sometimes more" |
|
Ok, let's merge then. Thanks a lot for looking into this. |
|
"Current" msys2 issues are in this ticket: msys2/setup-msys2#99 |
|
Probably worth merging into 3.4 branch too. |
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.
I tried here to work around the CI issues with mac on gh actions workers - turns out it's recent python 3.9 change :/ For some it's automagically fixed, for others not... So i had to use a workaround
Additionally:
nofeatures_nossetarget to check whether something won't blow up if there's no SSELinux-minimalchecking "basic compilers" all probable failures are checked early and so Linux, Windows & Mac targets are checked in parallel.This should make it easier to catch if PR is failing due to code rather than OS/Packaging problems
sidenote: msys2 still can fail with weird stuff. No workarounds for that except "try to restart action every 2-4 hours" :/