Skip to content

ci(stress): add integration test target to ci-stress workflow#253

Merged
codemonkeychris merged 1 commit into
mainfrom
ci-stress-integration
May 12, 2026
Merged

ci(stress): add integration test target to ci-stress workflow#253
codemonkeychris merged 1 commit into
mainfrom
ci-stress-integration

Conversation

@codemonkeychris
Copy link
Copy Markdown
Collaborator

Summary

  • Adds an integration-tests job to .github/workflows/ci-stress.yml that mirrors the existing unit/selftest stress matrix and runs tests/Reactor.IntegrationTests/.
  • Replaces the both target option with all (= unit + selftests + integration). Each suite can still be stressed individually via the target input.
  • Summary job now surfaces all three results.

Motivation: integration tests are starting to feel flaky in CI. This lets us dispatch N iterations across parallel shards to surface the offenders, the same way we use the workflow for unit/selftests.

Test plan

  • After merge, dispatch CI Stress from main with target=integration, iterations=100, shards=20 and verify per-shard logs identify any flakes.
  • Dispatch target=all once to confirm unit + selftests + integration paths all still wire up.

🤖 Generated with Claude Code

Adds an integration-tests job to ci-stress.yml that mirrors the existing
unit/selftests stress matrix but builds and runs Reactor.IntegrationTests.
Replaces the 'both' target choice with 'all' (unit + selftests + integration);
each suite can also be stressed individually. Summary job now reports all three
results.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@codemonkeychris codemonkeychris merged commit 1815233 into main May 12, 2026
31 checks passed
@codemonkeychris codemonkeychris deleted the ci-stress-integration branch May 12, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant