Pin rucc v0.18.8 in the kernel and nightly workflows - #38
Merged
Merged
Conversation
tamnd
added
kind/chore
8 of 17 tasks
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.
The workflows still downloaded rucc v0.17.0. kbuild probes the assembler with
-Wa,--version, which v0.17.0 does not take, so every rucc kernel build in CI stopped at configure. That also meant the nightly never got to grade kselftest. v0.18.8 is the first release since v0.18.0 to pass the release gate. The hash is the one in the published.sha256file, and I checked it against the downloaded tarball.Part of #6