Merged
Conversation
Member
Author
|
You can see on my AppVeyor instance the cache being loaded and also the parallel invocation for a branch vs a sequential invocation for the PR. |
This was referenced Apr 20, 2020
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
1 participant
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.
This morning I tweaked rolling builds configuration on AppVeyor to help the 4.11 release cycle. AppVeyor now cancels builds when a new commit is pushed either to a PR or to a branch. This should help, as multiple PRs merging clog up AppVeyor while it builds trunk commits which we already know will work.
This PR aims to lower the AppVeyor runtime a bit further with two headline changes:
make -j(AppVeyor workers have 2 vCPUs). I've done this for branches (i.e.trunkand4.11) since we expect these builds to pass and a failure means someone inadvertently messed up and will investigate urgently. I haven't done this PRs, because the logs become harder to read if there's an error and I don't want to encourage an attitude of "Oh, AppVeyor builds with-jso it's probably just a parallelism thing which we can fix later", given there's often already a "Oh, AppVeyor fails all the time, it's probably fine" 🙂configurescripts run hellishly slowly under Cygwin, because shell scripts hammerfork- I've increased the caching to keep the correctconfig.cachefile in place. Ifconfigurefails there's a single retry having blown away the cache. This shaves minutes off the build time...