Open adityamandaleeka opened 1 year ago
@amcasey
On my box, a successful run takes 6 seconds, so it might just be slow. I'll try to rediscover what it's doing.
From the line numbers, it seems like it's timing out on await appFuncCompleted.Task.DefaultTimeout();
, but that appears to be set before aborted.Task
, which has already been verified by that point.
I'm at 110 consecutive passes locally.
Edit: made it to 1000 consecutive passes. That doesn't mean it's not interacting badly with another test or something.
A local run did time out in Microsoft.AspNetCore.Server.Kestrel.Core.Tests.HttpConnectionTests.WriteDataRateTimeoutAbortsConnection
, which is closely related.
Edit: this test is much simpler and it checks for an abort exception before waiting for the event. Seems like it's probably just too slow to hit the 5 second deadline (on a machine with two virtual cores).
I just say this fail again on a Helix run for my PR targeting release/8.0. Was there ever a PR to quarantine this?
It was in the helix retry list, but I guess that's not enough.
Happening also with the non-https one. Using this issue to track both quarantined tests.
Details in this issue: https://github.com/dotnet/aspnetcore/issues/58169
Failing Test(s)
Error Message
Stacktrace
Logs
Build
https://dev.azure.com/dnceng-public/public/_build/results?buildId=368651&view=results