Fix linux build image in eng/pipelines/libraries/stress/http.yml

[akoeplinger]

@rzikm This fixes the disk space issue. It still fails to build with this error in the "Build HttpStress" step, do you have an idea:

Invalid interpolation format for "client" option in service "services": "${DOCKERFILE:-Dockerfile}"

[dotnet-policy-service]

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

[rzikm]

Hi, I don't know, we are using the same image for SslStress, with pretty much the same setup (we also use this envvar substitution in ssl stress compose file). Do we know the docker version on the image?

[rzikm]

/azp run runtime-libraries stress-ssl

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

I found some differences in the way docker-compose.yml was structured compared to SslStress, pushed the changes.

[akoeplinger]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[antonfirsov]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

@antonfirsov @rzikm looks like this will need a bit more attention than the quick fix I thought, would you mind taking over the PR?

[rzikm]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

thanks. something seems to be up with the http 3.0 stress test, if you click "View raw log" on AzDO you see this message from AddressSanitizer infinitely repeated:

2025-01-23T10:59:23.6426519Z [command]/usr/bin/bash /mnt/vss/_work/_temp/8a34c3e2-1855-4ac9-867d-b038953e79cb.sh
2025-01-23T10:59:24.1518371Z Creating network "httpstress_default" with the default driver
2025-01-23T10:59:24.2979341Z Creating httpstress_server_1 ... 
2025-01-23T10:59:24.9334260Z �[1A�[2K
2025-01-23T10:59:24.9335125Z Creating httpstress_server_1 ... �[32mdone�[0m
2025-01-23T10:59:24.9426960Z �[1BCreating httpstress_client_1 ... 
2025-01-23T10:59:25.3407238Z �[1A�[2K
2025-01-23T10:59:25.3411586Z Creating httpstress_client_1 ... �[32mdone�[0m
2025-01-23T10:59:25.3597575Z �[1BAttaching to httpstress_server_1, httpstress_client_1
2025-01-23T10:59:25.3600186Z client_1  | AddressSanitizer:DEADLYSIGNAL
2025-01-23T10:59:25.3604301Z client_1  | AddressSanitizer:DEADLYSIGNAL
2025-01-23T10:59:25.3607983Z client_1  | AddressSanitizer:DEADLYSIGNAL
2025-01-23T10:59:25.3626250Z client_1  | AddressSanitizer:DEADLYSIGNAL
2025-01-23T10:59:25.3627722Z client_1  | AddressSanitizer:DEADLYSIGNAL
2025-01-23T10:59:25.3629272Z client_1  | AddressSanitizer:DEADLYSIGNAL
...

[rzikm]

That's weird, I can't reproduce this locally, maybe we should disable address sanitizer for now

[rzikm]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[akoeplinger]

this might be related since we're now using Ubuntu 22.04 hosts: actions/runner-images#9524

[akoeplinger]

Looks like it's green now :)

[rzikm]

LGTM, Thanks!