-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
BinderTracingTest.ResolutionFlow.cmd timed out #37132
Comments
Failed again in #37254. |
Is the correct area assembly loader? |
Tagging subscribers to this area: @vitek-karas, @agocke |
Can we determine when was the last time we saw this failure? @elinor-fung added some fixes relatively recently to the binder tracing tests - maybe it has already been fixed. |
This test failed in my PR (CoreCLR Pri0 Runtime Tests Run Windows_NT arm checked).
|
The second failure makes no sense to me:
But that variable is initialized to the
This is the only
That place passes the argument as a value returned by either |
Failed in #41757 |
Note this failed again today. I've made this a live issue so failures will be tracked in the main body. |
I keep hitting the timeout locally on my macOS device consistently. |
@sywhang and I took a look at this. It is a product issue that can cause deadlocks. It can hit any test that uses tracing (like BinderTracingTest.Basic and BinderTracingTest.ResolutionFlow do). |
This was on Windows arm
https://dev.azure.com/dnceng/public/_build/results?buildId=662529&view=logs&j=3ce1ffe6-2daf-5d48-23b6-56961b8285e2&t=e1bc0efe-88b5-592d-ae74-0ec82e3852af&l=38
cc: @jashook who would be the right person to look into this?
Runfo Tracking Issue: Runtime failures in BinderTracingTest.ResolutionFlow
Build Result Summary
The text was updated successfully, but these errors were encountered: