Repository navigation
Conversation
…oes red Mutation check for the canary pull request. This branch is never merged; it is closed and deleted once its Canary run finishes.
Owner
Author
|
Mutation check done: Canary run 40979086697 selected only llama-cpu and went red (pull failed after 3 attempts: the digest does not exist). Closing; recorded in #258. |
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.
Mutation check for #258. This points llama-cpu's pin at a nonexistent tag (server-b99999) and digest, so the Canary run must go red. It targets the canary branch, not main, so only the Canary workflow runs. It is closed and its branch deleted once the run finishes.