Add CI test to exercise gcc10 #2590
Merged
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
* Turns out no code changes were needed for gcc10! * Also updated some dependency ranges in INSTALL.md. * Make a new CI test "latest" -- using the latest supported release of the toolchain and dependencies. That includes gcc10 in this case. (This is different than the "bleeding edge" test, which tests against the development master of many dependencies.) * Make several test matrix entries (including bleeding edge, static libs, and sanitizers) no longer test on every push. That makes things take too long. They all still run nightly, and if you're pushing a branch with the name "RB", "release", or "master", so they will catch problems before releases. Also, all tests run any time the branch name is "gh", so if you are preparing a patch specifically to make changes to CI, make sure to do that. We will probably continue to fine-tune exatly when we run all tests, versus the common configurations. Signed-off-by: Larry Gritz <lg@larrygritz.com>
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.
Turns out no code changes were needed for gcc10!
Also updated some dependency ranges in INSTALL.md.
Make a new CI test "latest" -- using the latest supported release of
the toolchain and dependencies. That includes gcc10 in this case.
(This is different than the "bleeding edge" test, which tests against
the development master of many dependencies.)
Make several test matrix entries (including bleeding edge, static
libs, and sanitizers) no longer test on every push. That makes
things take too long. They all still run nightly, and if you're
pushing a branch with the name "RB", "release", or "master", so they
will catch problems before releases. Also, all tests run any time
the branch name is "gh", so if you are preparing a patch
specifically to make changes to CI, make sure to do that. We will
probably continue to fine-tune exatly when we run all tests, versus
the common configurations.
Signed-off-by: Larry Gritz lg@larrygritz.com