-
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 System.Transactions.Tests.OleTxTests.ImplicitDistributedTransactions_cannot_be_changed_after_being_read_as_true #77241
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. |
Tagging subscribers to this area: @roji Issue DetailsRun: runtime-coreclr libraries-jitstress 20221019.1 Failed test:
Error message:
|
I'm OOF for the next week so won't be able to look into this... But could this be related to the RemoteExecutor rather than to distributed transactions? Or is there a way to get more visibility on what's going on there? /cc @stephentoub |
Failed again in: runtime-coreclr libraries-jitstress 20221027.1 Failed test:
Error message:
|
Thanks, I'll be looking into this, but it may take a bit of time due to other priorities. |
Failed again in: runtime-coreclr libraries-jitstress2-jitstressregs 20221105.1 Failed tests:
Error message:
Stack trace:
|
@roji Can we disable the test in the meantime? We hit this frequently on JIT pipelies. |
Sorry for the delay on this, am currently away on vacation. Will fix or disable the test tomorrow. |
No worries, enjoy your vacation. |
Failed in Run: runtime-coreclr libraries-jitstress 20221113.1 Failed tests:
Error message:
Stack trace:
|
The failures reports above are all from jitress on arm64 on Windows, and seems to indicate a timeout from RemoteExecutor (see #74320 for a general discussion on unexplained RemoteExecutor timeouts, mostly on jitstress). I can't think of a specific reason for the test being hung, so for now I'll disable the test to avoid further failures, and to check whether the hanging/timeout moves to another test (in case the hanging depends on timing). |
Run: runtime-coreclr libraries-jitstress 20221019.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: