Retry failing helix test

[amcasey]

Http2WebSocketTests.HEADERS_Received_SecondRequest_ConnectProtocolReset failed in #48664

[ghost]

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

[BrennanConroy]

Issue? Link to failure?

[amcasey]

Sorry, a bit rushed today. Failure: https://github.com/dotnet/aspnetcore/runs/14144482654

Was I supposed to file a corresponding issue? I didn't notice that in the handbook instructions.

[ghost]

Hi @amcasey. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[amcasey]

My reading of these steps was, don't follow the quarantine procedure (including filing an issue and adding an attribute) if you can add it to the retry list. I agree that it's a little weird that there will be no (apparent?) follow-up if the test passes on retry.

[ghost]

Hi @amcasey. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[BrennanConroy]

Was I supposed to file a corresponding issue? I didn't notice that in the handbook instructions.

It's possible the instructions changed. The whole retry thing is kind of new (and I'm not a fan of it anyways 😆)

Also, that failure looks very similar to the PR Will pinged us on yesterday...

[amcasey]

Also, that failure looks very similar to the PR Will pinged us on yesterday...

That was in release/6.0 and I was unable to repro it in main. Fair point though.

[ghost]

Hi @amcasey. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.