-
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.TransactionManagerTest.DefaultTimeout_MaxTimeout_Set_Get #90085
Comments
Tagging subscribers to this area: @roji, @ajcvickers Issue DetailsFailed in: runtime-coreclr libraries-pgo 20230806.1 Failed tests:
Error message:
Stack trace:
|
Work was recently done in these Invoker paths. /cc @steveharter |
Failed again in: runtime-coreclr libraries-jitstress 20240103.5 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-pgo 20240211.1 Failed tests:
Error message:
Stack trace:
|
@AndyAyersMS Looks like it mostly fails in PGO stress? |
The test is [Fact]
public void DefaultTimeout_MaxTimeout_Set_Get()
{
TimeSpan tsDefault = TimeSpan.Parse("00:02:00");
TransactionManager.DefaultTimeout = tsDefault;
Assert.Equal(tsDefault, TransactionManager.DefaultTimeout); where the initial value of the default timeout is The property getter/setter is nontrivial runtime/src/libraries/System.Transactions.Local/src/System/Transactions/TransactionManager.cs Lines 292 to 344 in eece6a6
The original PR #71703 noted there was a potential problem with tearing reads on a 32 bit platform, I wonder if it is still there but just harder to observe, and these tests manage to delay execution just the right way (on occasion). FYI @mconnew in case this is a latent test issue. |
Failed in: runtime-coreclr libraries-pgo 20240310.1 Failed tests:
Error message:
Stack trace:
|
Seems to no longer be a problem. |
Failed in: runtime-coreclr libraries-pgo 20230806.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: