-
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
JIT tests - Unhandled IOException connection timed out #75867
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis might be related to #75391 but it's the first time I see the failure message so I'm opening a new issue to be safe. Need help confirming if related to the above or not, and also need help determining if this failure needs a fix backported to the 7.0-rc2 or the 7.0 branch. Found in this
Callstack
|
@rainersigwald / @rokonec / @AR-May / @MichalPavlik this is happening in a few PRs in release/7.0-rc2. We found it in this other PR: #75885 |
cc @marcpopMSFT for risk on MSBuild Server. |
I just noticed that among the several different failures reported in this other general JIT issue, this one was already reported there: #75391 I'm not sure if we can consider all the failure messages related to the exact same root cause, but I wanted to mention the other issue in case we need to close this one as duplicate. cc @radical who opened the other one. |
Based on the log file/MSBuild stack trace, I would say that the root cause is same as for #75391. I will create issue in MSBuild repo. |
@carlossanlop The root cause of this bug is not obvious from logs. Is there a way we can somehow repro it locally? Or at least run it in CI as debug so we have more precise exception stack? |
closing as a duplicate of #75391 (which appears to have resolved by disabling the compilation server) |
Occurrences: (happens during random JIT tests)
Original report
This might be related to #75391 but it's the first time I see the failure message so I'm opening a new issue to be safe.
Need help confirming if related to the above or not, and also need help determining if this failure needs a fix backported to the 7.0-rc2 or the 7.0 branch.
Found in this
release/7.0-rc2
deps update PR: #75675Console log
The text was updated successfully, but these errors were encountered: