Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unrecognized labels cancel entire workflow
See original GitHub issueFrom https://github.com/CloudSnorkel/cdk-github-runners/issues/72#issuecomment-1289480905
In your case it sounds like it’s because we expect every job with the
self-hostedlabel to also have a label we recognize. It sounds like you have multiple installations ofcdk-github-runnersin different accounts, each implementing different labels. That means some of the installations will not recognize the label and cancel the job. We can probably add a flag to disable this behavior. Let’s do this in a separate ticket.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
😮 thanks @laxgoalie392 - had the same issue - we had pretty weird issues because it even cancelled the jobs for other runners that were not created via this solution …
thanks! i usually just look at the changes in the PR and apply them manually. not a perfect verification method but quickly does a good enough job i think