Variant of "Nix cache enhancement in CI and ping clang-tools version to 17.0.6 " #253
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
nixos 24.05 channel is updated to the latest commit a3f9ad65a0bf298ed5847629a57808b97e6e8077 as well Signed-off-by: Thing-han, Lim <[email protected]>
Now the shell becomes - default, ci-linter: same as before, not changed - ci: native shell - ci-cross: shell equipped with both native and cross compiled gcc and glibc (would be slow on the first build) - ci-cbmc: native shell with cbmc - ci-cbmc-cross: ci-cross shell with cbmc Signed-off-by: Thing-han, Lim <[email protected]>
…stem configuration - Linux runner with root user: install with single-user mode - Linux runner with non-root user or macOS runner: install with multi-user mode Signed-off-by: Thing-han, Lim <[email protected]>
magic-nix-cache runs into GH rate limit easily, and ec2 instance somehow cannot restore magic-nix-cache. cache-nix-action would save a whole nix shell in GH cache, which can be sharable between branches, thus speeding up CI. Hash of nix files is used as cache suffix, so that cache sharing between branch should be safe '-multi' suffix for cache prefix is added if installed in multi-user mode, to avoid cache pollution Signed-off-by: Thing-han, Lim <[email protected]>
Disable linting for ec2_all as it doesn't add much value when there's already an linting job on GH shared x86_64 runner Run linting first for all ec2 if linting is enabled Use ubuntu-latest instead of pqcp-x64 for matrix, since once the matrix is all excluded (when pushed to fork), the following jobs that depends on this won't be executed Signed-off-by: Thing-han, Lim <[email protected]>
Signed-off-by: Hanno Becker <[email protected]>
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.
This is an almost-copy of #233 removing the commit on propagation of GH access tokens which I don't yet understand and would like to discuss further merging. Opening this version to check whether the performance gains are still similarly pronounced, in which case this version can move forward and propagations of tokens follows in due cause.