CI: Add more legacy compiler tests and move to scheduled workflow #1132
Merged
Conversation
Our compiler tests and constant-time tests have been steadily growing over time which is not sustainable in the medium term. This commit solves that by splitting the set of compiler versions into two 1) Per-PR compilers - tested on every PR. For each family (gcc, clang, zig) we keep the oldest available version plus the three latest ones. 2) Legacy compilers - all versions, tested in a scheduled job or when the `legacy-compiler-tests` label is added to the PR. Currently the job is scheduled to run daily, but in the long term we may want to switch it to weekly. This allows us to extend compiler coverage by gcc 6, 8, 9, 10, zig 0.10+0.11, and clang 6..13 for both CT and compiler tests. My expectation is that the legacy compilers only get changed whenever nixpkgs drops a compiler version. Signed-off-by: Matthias J. Kannwischer <matthias@zerorisc.com>
Signed-off-by: Matthias J. Kannwischer <matthias@zerorisc.com>
Merged
hanno-becker
approved these changes
May 27, 2026
Contributor
CBMC Results (ML-DSA-87, REDUCE-RAM)Full Results (200 proofs)
|
Contributor
CBMC Results (ML-DSA-65, REDUCE-RAM)Full Results (200 proofs)
|
Contributor
CBMC Results (ML-DSA-44, REDUCE-RAM)Full Results (200 proofs)
|
Contributor
CBMC Results (ML-DSA-87)Full Results (200 proofs)
|
Contributor
CBMC Results (ML-DSA-44)Full Results (200 proofs)
|
Contributor
CBMC Results (ML-DSA-65)Full Results (200 proofs)
|
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.
Our compiler tests and constant-time tests have been steadily
growing over time which is not sustainable in the medium term.
This commit solves that by splitting the set of compiler versions
into two
Per-PR compilers - tested on every PR. For each family (gcc, clang,
zig) we keep the oldest available version plus the three latest ones.
Legacy compilers - all versions, tested
in a scheduled job or when the
legacy-compiler-testslabel is addedto the PR. Currently the job is scheduled to run daily, but in the long
term we may want to switch it to weekly.
This allows us to extend compiler coverage by gcc 6, 8, 9, 10, zig
0.10+0.11, and clang 6..13 for both CT and compiler tests.
My expectation is that the legacy compilers only get changed
whenever nixpkgs drops a compiler version.