[HTTP] Stress fix for docker compose

[ManickaP]

Wind down docker compose between individual runs in HTTP stress.

See logs for error: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_apis/build/builds/1136356/logs/18
And test run of my branch that passed: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_apis/build/builds/1137026/logs/17

[ManickaP]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This PR fixes a Docker Compose cleanup issue in the HTTP stress test pipeline by adding explicit docker-compose down commands after each stress test run. The change ensures proper resource cleanup between individual HTTP protocol version tests (3.0, 2.0, and 1.1) to prevent conflicts and failures in subsequent test runs.

Key changes:

• Added docker-compose down command after each HTTP stress test execution
• Applied consistently across all three HTTP protocol version tests (3.0, 2.0, 1.1)

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[ManickaP]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ManickaP]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ManickaP]

Http stress is green: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1138189&view=results
@dotnet/ncl please another quick review here.

The fix is based on the second answer here: https://askubuntu.com/questions/1508129/docker-compose-giving-containerconfig-errors-after-update-today as we don't have docker compose in the images yet.

[ManickaP]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/17544665607

[ManickaP]

/backport to release/9.0-staging

[github-actions]

Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/17544677561

[ManickaP]

/backport to release/10.0

[github-actions]

Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/17544683950

[github-actions]

@ManickaP backporting to "release/8.0-staging" failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Wind down docker compose between individual runs in HTTP stress
Using index info to reconstruct a base tree...
M	eng/pipelines/libraries/stress/http.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/libraries/stress/http.yml
Applying: Experiment 2
Using index info to reconstruct a base tree...
M	eng/pipelines/libraries/stress/http.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/libraries/stress/http.yml
CONFLICT (content): Merge conflict in eng/pipelines/libraries/stress/http.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Experiment 2
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

[github-actions]

@ManickaP backporting to "release/9.0-staging" failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Wind down docker compose between individual runs in HTTP stress
Using index info to reconstruct a base tree...
M	eng/pipelines/libraries/stress/http.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/libraries/stress/http.yml
Applying: Experiment 2
Using index info to reconstruct a base tree...
M	eng/pipelines/libraries/stress/http.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/libraries/stress/http.yml
CONFLICT (content): Merge conflict in eng/pipelines/libraries/stress/http.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Experiment 2
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!