ci: test upcoming Cranelift release branch#1643
Open
0xmuon wants to merge 1 commit intorust-lang:mainfrom
Open
ci: test upcoming Cranelift release branch#16430xmuon wants to merge 1 commit intorust-lang:mainfrom
0xmuon wants to merge 1 commit intorust-lang:mainfrom
Conversation
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.
Fix: #1626
Added a scheduled workflow that patches
Craneliftdeps to the latestwasmtimerelease-*branch and runs the test suite.Doubt:
In this new workflow I am using an Actions cache key
cranelift-release-tested-${branch}to skip rerunning once a givenWasmtimerelease-*branch has been tested. Is that acceptable, or would you prefer it to always run (or like re run weekly) even for the same branch to catch regressions fromcg_clifchanges?