Skip to content

Add CI job to stress-test changed Go packages on PRs#7417

Draft
CharlieTLe wants to merge 1 commit intocortexproject:masterfrom
CharlieTLe:ci/stress-test-changed-packages
Draft

Add CI job to stress-test changed Go packages on PRs#7417
CharlieTLe wants to merge 1 commit intocortexproject:masterfrom
CharlieTLe:ci/stress-test-changed-packages

Conversation

@CharlieTLe
Copy link
Copy Markdown
Member

Summary

  • Adds a PR-only, non-blocking (continue-on-error: true) CI job that detects which Go packages changed and reruns their tests with -count 5 to catch flaky/non-deterministic failures before merge
  • Adds a test-stress Makefile target that accepts STRESS_TEST_PACKAGES and runs them without -race (the main test job already covers that)
  • Detection filters out vendor/ and integration/ directories and only tests packages containing _test.go files

Test plan

  • Open this PR and verify the test-stress job appears in the CI checks
  • Verify it detects the changed Makefile/workflow files correctly (should find no testable Go packages and skip)
  • Push a trivial Go test file change and verify it runs stress tests on the correct package
  • Verify a PR with only non-Go file changes skips the test step gracefully

🤖 Generated with Claude Code

Add a non-blocking CI job that detects which Go packages changed in a PR
and reruns their tests with -count 5 to surface flaky/non-deterministic
failures before they merge.

The job:
- Only runs on pull requests (not pushes to master)
- Uses continue-on-error so it never blocks merging
- Runs on a single ubuntu-24.04 runner to minimize cost
- Filters out vendor/ and integration/ directories
- Only tests packages that contain _test.go files
- Skips entirely if no testable Go packages changed

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Charlie Le <charlie_le@apple.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant