-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: cleanup MSYS2 related builds and scripts #11124
Conversation
e4c3f68
to
7241b03
Compare
Truthfully, I did not even notice appveyor was failing until earlier this week... the time spent fixing it is appreciated, but I'm not even sure if we still want it. Does it really do us any good? Maybe we should just keep the MSYS2 to github actions move and delete appveyor (there were previous PR attempts at this actually). Not sure what everyone else thinks. |
I will let you decide. Indeed having msys2 build both in GH Actions and AppVeyor is kind of the same, but the overhead of having both is minimal, hence I didn't propose in this PR to remove the AppVeyor one. If anything this would allow to simplify it even further, but not much difference really. EDIT: Without appveyor it would look like this kasper93@1957ca5 could also add waf, but it fails in my test VM and I didn't look why. |
Personally I'm fine with just fixing appveyor and continuing to use it. |
msys2 does not use WAF build system. Removing it from CI would be another choice. If you want to keep old slower Appveryor adding --- a/TOOLS/appveyor-build.sh
+++ b/TOOLS/appveyor-build.sh
@@ -6,6 +6,7 @@ export CC=gcc
export PKG_CONFIG=/usr/bin/pkg-config
export PERL=/usr/bin/perl
export PYTHON=/usr/bin/python3
+export WAF_NO_PREFORK=1
"$PYTHON" bootstrap.py
"$PYTHON" waf configure \ |
Yes, I know. There is also another underlying issue with waf on MSYS2. I didn't have time to push changes, but it was working last week, just need to put in on this branch. |
Ok, updated. After looking at this I decided to remove AppVeyor. It does not bring any value, it is run only on master branch (and no one is looking at the status) and is exactly the same environment that I added just now to GH actions, which will run also on PRs. I'm open to discussion, having it supported is just a few scripts, but it really would be the same as current gh build... To summary the changes:
overall small changes... |
76592b6
to
c45eda2
Compare
I see that you put the commands for the msys2 build directly in the github workflow. Could you instead rework it so it's in its own |
@Dudemanguy done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't verify the waf weirdness or the zimg test thing myself, but I'll assume they work.
6997b1f
to
adcfc86
Compare
MSVC is not supported and waf doesn't respect CC environment value like any sane buildsystem.
Fixes tests on 32-bit platforms
Frankly I don't care about msys2 build itself, but isn't it annoying for you guys that ci is red on master branch? This fixes timeout of appveyor and add github workflow, because why not.