-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 System.Net.Quic.Tests.QuicStreamTests.ReadWrite_Random_Success #86565
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRun: runtime-coreclr libraries-jitstress 20230519.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr libraries-jitstressregs 20230618.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr libraries-pgo 20230813.1 Failed tests:
Error message:
Stack trace:
|
Hi @wfurt, do you think this bug will be investigated? |
Failed again in: runtime-coreclr libraries-pgo 20230910.1 Failed tests:
Error message:
Stack trace:
|
Adding the
|
Failed again in: runtime-coreclr libraries-jitstress 20230925.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr libraries-pgo 20231022.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr libraries-jitstress 20231028.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr libraries-pgo 20231207.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr libraries-jitstress 20231215.1 Failed tests:
Error message:
Stack trace:
|
@wfurt @ManickaP @karelz Marking these tests as long-term "Known Build Failure" is not acceptable, as outerloop pipelines do not get "Known Build Failure" processing and filtering, so noise from these failures continues to affect us. If they can't be made to run reliably on arm32 or under stress modes, can you please disable them under those modes? There is some information on disabling tests here and here. For instance, maybe:
? |
Another alternative is to disable these tests entirely from "normal" runs and only run them in specific System.Net test pipelines under only the parameters you control, and not subject to the usual test monitoring. |
Disabling these tests for jit stress and similar seems reasonable. I'll look into it. |
Run: runtime-coreclr libraries-jitstress 20230519.1
Failed test:
Error message:
Known issue validation
Build: 🔎⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line.
Result validation:
Validation performed at: 9/22/2023 4:22:03 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: