Skip Daily Tests for Version changes - #4255
Conversation
📝 WalkthroughWalkthroughThe daily GitHub Actions workflow now ignores pull requests that only change ChangesDaily workflow filtering
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
3a1117c to
71e9e2a
Compare
|
The DCO check is failing: commit 3a1117c ( |
There was a problem hiding this comment.
The paths-ignore addition is correct for the stated goal: GitHub skips the workflow only when every changed file matches an ignore pattern, so version-bump/release-notes PRs (src/version.h + 00-RELEASENOTES/markdown) stop triggering the daily suite, while any PR touching version.h alongside code still runs it. ci.yml and the other workflows do not ignore src/version.h, so regular CI still covers version-only PRs, and the schedule/workflow_dispatch/workflow_call triggers are unaffected by path filters. No issues with the change itself; the only blocker is the missing DCO sign-off noted separately.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## unstable #4255 +/- ##
============================================
- Coverage 76.89% 76.79% -0.11%
============================================
Files 162 162
Lines 81487 81487
============================================
- Hits 62663 62581 -82
- Misses 18824 18906 +82 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
But we need to implement a signoff strategy on the versions with the failing tests, even if they are flaky.
Right now we are quite hand wavy about how we treat the flaky tests for daily failures on release notes PRs.
Now that we will skip the daily run, we should have the release owner add a signoff of the tests that failed on the last daily run on the release branch, and why we are moving forward with the release.
I think that's a good point. There could be scenarios where the release owner does not have the visibility about daily test failures on that branch. I don't feel too strongly about this anymore. I will close this for now. This seems like a good gate to have. |
Currently, we run all the daily tests whenever a PR is raised to one of the released branches.
We have started to automate the release process with automated release notes PR like #4247.
Daily tests are time consuming and often flaky. I think we do not need to run daily tests on these PRs, and CI could still be a good sanity check for
version.hfile changes.This can help the release notes PR to be ready faster.