Re-run checks not working when there is a filter
See original GitHub issueHello,
One of the steps
in the Job
didn’t pass and so the github action check has failed.
Then I triggered the Re-run checks
without changing anything. The build has skipped the step
which was failed and the check has passed. Ideally It should fail again. This is not the first time, I have checked multiple times with different workflows.
After Triggering Re_run checks
Please ask me if something is not clear.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (6 by maintainers)
Top Results From Across the Web
What happened to the rerun button in GitHub checks?
1 Answer 1 · either those checks are not failed · or there is a permission issue which would make your profile unable...
Read more >Rerun the 24x7 and Daily Safety Checks - N-able
Rerun the 24x7 and Daily Safety Checks. Occasionally it may be necessary to rerun the 24x7 or Daily Safety Checks directly from the...
Read more >Running GitHub Actions only on certain pull requests
Configure your workflow to be triggered when a pull request's label changes, and filter based on the label's presence.
Read more >Add "Passed on rerun" to test failure report not only to each ...
Hello,. currently I only see the option to filter for "Passed on rerun" tests on each pipeline/build run. But in order to get...
Read more >Status checks for your instances - AWS Documentation
Monitor instances with status checks to determine whether Amazon EC2 has detected any problems with your instances.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ibakshay - Some coworkers are putting a fix together that I believe will address this for you. I don’t have an ETA for you though. This issue is staying in my inbox so I don’t forget to report back 😉
@ibakshay - I don’t know for sure about this exact example, but we are working on some fixes related to re-runs in particular, where the event data on the rerun isn’t exactly the same as the original event data.
I’ll link this issue with our internal tracking issue for that work and do my best to remember to let you know here when we’ve deployed any changes. Thanks for the feedback!