-
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
Test failure: Loader\\binding\\tracing\\BinderTracingTest.ResolutionFlow\\BinderTracingTest.ResolutionFlow.cmd #92236
Labels
area-Tracing-coreclr
blocking-clean-ci-optional
Blocking optional rolling runs
JitStress
CLR JIT issues involving JIT internal stress modes
Known Build Error
Use this to report build issues in the .NET Helix tab
os-windows
Milestone
Comments
Here's another case, also win-x86, but a different JIT stress run. |
cc @tommcdon |
I'm still seeing many failures of this test, e.g.: |
The fix in #92431 introduced another deadlock, I will open a fix soon |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-Tracing-coreclr
blocking-clean-ci-optional
Blocking optional rolling runs
JitStress
CLR JIT issues involving JIT internal stress modes
Known Build Error
Use this to report build issues in the .NET Helix tab
os-windows
pipeline: runtime-coreclr jitstress-isas-x86
job: coreclr windows x86 Checked jitstress_isas_x86_nosse3_4 @ Windows.10.Amd64.Open
hang? hit a 30m timeout.
https://dev.azure.com/dnceng-public/public/_build/results?buildId=408841&view=ms.vss-test-web.build-test-results-tab&runId=8882878&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=120623
@davmason
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=408841
Error message validated:
BinderTracingTest.ResolutionFlow.(sh|cmd) Timed Out
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 9/27/2023 9:50:29 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: