-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure WaiterRemovedAfterDispose #5450
Comments
FYI @RussKie - last time you wanted to investigate, rather than skip |
@dotnet/dotnet-extensions-fundamentals please triage |
I'm checking this one, verifying it's a problem with test itself or the actual logic. Can't assign the issue to myself yet due to lack of permissions. |
To me it sounds like it could be problem with resource utilization on the agent running the build and unexpected behavior on memory or GC.
For 1st point I'm not really sure how to look for more details. But for second we can exclude it if we check |
I'll be checking pipelines from time to time, but let me know in case there's new failure. |
This submission has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 14 days. It will be closed if no further activity occurs within 7 days of this comment. |
Microsoft.Extensions.Time.Testing.Test.TimerTests.WaiterRemovedAfterDispose
https://dev.azure.com/dnceng-public/public/_build/results?buildId=818533
The text was updated successfully, but these errors were encountered: