Another attempt to fix stress tests#83211
Conversation
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAttempt to fix #82528, using a workaround from actions/runner-images#7080 (comment).
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
1 similar comment
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
1 similar comment
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
/azp run runtime-libraries stress-ssl |
|
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
antonfirsov
left a comment
antonfirsov
left a comment
There was a problem hiding this comment.
@dotnet/ncl this seems to work, can someone take a look?
| $dockerComposeCmd = $env:DOCKER_COMPOSE_CMD | ||
| if (!(Test-Path $dockerComposeCmd)) { | ||
| $dockerComposeCmd = "docker-compose" | ||
| } |
There was a problem hiding this comment.
This is now an asymmetry between run-docker-compose.ps1 in SslStress vs HttpStress.
For some reason, the HttpStress pipeline is ok to docker-compose build with V1 of compose but then do the run with V2, however in SslStress this resulted in a failure.
I don't want to add an equivalent workaround to run-docker-compose.ps1 in HttpStress, when it's not necessary.
ghost
locked as resolved and limited conversation to collaborators
3 participants
Tried using another Windows image, which did not work (#82736), so decided to go with the workaround from actions/runner-images#7080 (comment) to fix #82528.