-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Long Running Test: Interop/MonoAPI/MonoMono/PInvokeDetach/PInvokeDetach.sh #73040
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
/cc @SamMonoRT |
6 unique hits per Runfo table above as of 8/5, incl. 1 Rolling run - 1909685 on 7/28 AM (2nd run) |
I can't reproduce this or investigate it. Also this hang seems to have happened only once. I think we should close this for now. |
It happened twice - see updated top post (from manual search of last 30 days of failures). Removing 'blocking-clean-ci' label as it does not happen that often yet. |
If the crash dump would contain the runtime stacktrace, fixing this might be pretty easy. Not sure if there is a problem in the infrastructure that prevents this. Moving to 8.0 for now since it doesn't look like I will be able to investigate this anytime soon. |
Seen in an unrelated Queues:
Callstack
Callstack
|
Failures 7/5-8/5 (Runfo for last 30 days):
Note: The other failures associated by Runfo are unrelated to this issue.
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-71203-merge-9a2f7270283440c1b0/Interop/1/console.18899052.log?%3Fhelixlogtype%3Dresult
Runfo Tracking Issue: interop work item
Build Result Summary
The text was updated successfully, but these errors were encountered: