Conversation
Owner
Author
|
(the documentation commit also needs to be updated if we go this approach) One downside of not running CI on branch pushes, is that if you push a new branch and then open a PR, the tasks are incorrectly marked as skipped. Meanwhile, cirrus is running them (see https://cirrus-ci.com/build/5369972625506304). 
This updates as CI instances finish: 
|
This reverts commit ecf01f4.
Sjors
force-pushed
the
2024/02/ci-test-2
branch
from
ca5ad4a to
6537a2b
Compare
Sjors
force-pushed
the
2024/01/ci-test
branch
from
745e657 to
4ebcd96
Compare
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.
Same as #30 but instead of disabling workers for missing architectures, leave the tasks hanging (forever).