chore(test): fix CI test selection for adversarial and recipe suites#957
Conversation
Keep adversarial coverage available on demand while excluding these high-load edge-case suites from default pytest runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Use the production AIPerf builder runner for the integration-test matrix instead of GitHub-hosted Ubuntu. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Run integration CI on the production builder with the same setup, uv cache, and xdist worker cap used by unit tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Anthony Casagrande <acasagrande@nvidia.com>
Try out this PRQuick install: pip install --upgrade --force-reinstall git+https://github.com/ai-dynamo/aiperf.git@b9063ad46d61dc025b1fd457c505bb00dfae26f1Recommended with virtual environment (using uv): uv venv --python 3.12 && source .venv/bin/activate
uv pip install --upgrade --force-reinstall git+https://github.com/ai-dynamo/aiperf.git@b9063ad46d61dc025b1fd457c505bb00dfae26f1Last updated for commit: |
WalkthroughIntegration test CI workflow updated to modernize tooling and add xdist worker capping; nineteen adversarial test modules marked with ChangesCI Infrastructure and Test Stress Marking
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Restore unit adversarial tests to the default test selection while leaving component-integration adversarial stress markers intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Anthony Casagrande <acasagrande@nvidia.com>
Fail early when the mock server package or CLI entry point is missing, and tighten logger capture tests to target the modules that emit their records. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Undo the branch-specific integration workflow runner and setup changes while keeping the mock-server install guard in Makefile. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Run unit, component-integration, and integration stress tests as separate pytest invocations so stress-marked tests remain reachable by Makefile targets. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Anthony Casagrande <acasagrande@nvidia.com>
…957) Signed-off-by: Anthony Casagrande <acasagrande@nvidia.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
make test-stressso unit, component-integration, and integration stress tests are all reachable via separate pytest invocations.Test plan
uv run pytest tests/unit/ --collect-only -m 'stress' -quv run pytest tests/component_integration/ --collect-only -m 'stress' -quv run pytest tests/integration/ --collect-only -m 'integration and stress' -quv run pytest tests/integration/test_search_recipes.py --collect-only -m 'integration and not performance and not ffmpeg and not stress and not slow' -qconfirms search-recipe slow tests are deselected🤖 Generated with Claude Code