-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[release/8.0-staging][HTTP] Stress fix for docker compose #119454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a stress testing issue by adding proper cleanup between HTTP stress test runs. It ensures that Docker Compose is properly wound down before starting each test iteration to prevent resource conflicts and ensure clean test environments.
Key changes:
- Added
docker compose down
commands before each HTTP stress test run - Applied to both HTTP 2.0 and HTTP 1.1 test scenarios
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
HTTP stress is running and green: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1142009&view=results |
Test only change, tell-mode. |
/ba-g #117731 |
Backport of #119274 to release/8.0-staging
/cc @ManickaP
Customer Impact
Wind down docker compose between individual runs in HTTP stress.
Regression
Infra update.
Testing
CI stress runs.
Risk
Low. Test only change.