Skip to content
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

Outer Loop OpenSUSE 42.1 Debug: Test "System.Data.SqlClient.Tests.DiagnosticTest.ExecuteReaderTest" failed with "Xunit.Sdk.EqualException" #19983

Closed
KristinXie1 opened this issue Jan 22, 2017 · 23 comments
Assignees
Labels
area-System.Data.SqlClient test-run-core Test failures in .NET Core test runs
Milestone

Comments

@KristinXie1
Copy link

Failed Test: System.Data.SqlClient.Tests.DiagnosticTest.ExecuteReaderTest

Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_opensuse42.1_debug/lastFailedBuild/consoleText

Message:

System.Data.SqlClient.Tests.DiagnosticTest.ExecuteReaderTest [FAIL]
        Assert.Equal() Failure
        Expected: b6bade04-7eda-4678-a918-24502a6d7149
        Actual:   0893cbea-49ac-4282-9385-0a5060b6ee79

Stack Trace:

/mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/tests/FunctionalTests/DiagnosticTest.cs(458,0): at System.Data.SqlClient.Tests.DiagnosticTest.<>c__DisplayClass27_0.<CollectStatisticsDiagnostics>b__0(KeyValuePair`2 kvp)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/tests/FunctionalTests/FakeDiagnosticListenerObserver.cs(35,0): at System.Data.SqlClient.Tests.FakeDiagnosticListenerObserver.FakeDiagnosticSourceWriteObserver.OnNext(KeyValuePair`2 value)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Diagnostics.DiagnosticSource/src/System/Diagnostics/DiagnosticListener.cs(192,0): at System.Diagnostics.DiagnosticListener.Write(String name, Object value)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlClientDiagnosticListenerExtensions.cs(66,0): at System.Data.SqlClient.SqlClientDiagnosticListenerExtensions.WriteCommandAfter(DiagnosticListener this, Guid operationId, SqlCommand sqlCommand, String operation)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlCommand.cs(1370,0): at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlCommand.cs(1331,0): at System.Data.SqlClient.SqlCommand.ExecuteReader()
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/tests/FunctionalTests/DiagnosticTest.cs(119,0): at System.Data.SqlClient.Tests.DiagnosticTest.<ExecuteReaderTest>b__10_0()
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/tests/FunctionalTests/DiagnosticTest.cs(585,0): at System.Data.SqlClient.Tests.DiagnosticTest.CollectStatisticsDiagnostics(Action sqlOperation)
           /mnt/resource/j/workspace/dotnet_corefx/master/outerloop_opensuse42.1_debug/src/System.Data.SqlClient/tests/FunctionalTests/DiagnosticTest.cs(110,0): at System.Data.SqlClient.Tests.DiagnosticTest.ExecuteReaderTest()
@danmoseley
Copy link
Member

@saurabh500

@saurabh500
Copy link
Contributor

@tstringer Can you or someone from your team look at this issue?

@danmoseley
Copy link
Member

@tstringer ?

@trstringer
Copy link
Contributor

@JiayiLi1 was it just in openSUSE that you ran into this issue? I don't see why this would be a distro-specific issue. Do you have any other surrounding information on this? Did your tests run successfully on Ubuntu?

@tarekgh
Copy link
Member

tarekgh commented Feb 10, 2017

@KristinXie1
Copy link
Author

@tstringer it is just in openSUSE, If I ran into this issue on other OS system, I will update the comment here.

@trstringer
Copy link
Contributor

@JiayiLi1 what are the .net core build steps for openSUSE 42.x? I don't see anything documented. Do you have a quick list of zypper packages required on the host?

@trstringer
Copy link
Contributor

@JiayiLi1 can you please link me to the test failure instead of just the console output?

If this is related to the issue that @tarekgh pointed out, then there is an underlying problem outside of the diagnostics:

System.Data.SqlClient.SqlException : A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 2 - Connection was terminated)

That's a transport layer issue.

cc @saurabh500

@KristinXie1
Copy link
Author

@tstringer The link is https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_opensuse42.1_debug/77/

It is failed on build#77, but this page could not be found now.

@trstringer
Copy link
Contributor

@JiayiLi1 Can you please reproduce the issue through CI so that we can have the full picture of the failure?

@KristinXie1
Copy link
Author

@danmosemsft Can you do a favor? Since I couldn't navigate to the previous builds, the page could not be found, https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_opensuse42.1_debug/ there only shows recent 20 builds, but this issue is repro on build#77.

@danmoseley
Copy link
Member

@JiayiLi1 after a while (?2 weeks) the log are deleted. If the log is gone, there is nothing that can be done. If there is a newer build with a failure, please link that. If there is not, please close this until there is one.

@KristinXie1
Copy link
Author

@danmosemsft Thanks Dan, I will check this issue on next few builds.

@stephentoub
Copy link
Member

@stephentoub
Copy link
Member

@KristinXie1
Copy link
Author

KristinXie1 commented Feb 20, 2017

This issue is repro on InnerLoop_PortableLinux_release (build#296).

Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/portablelinux_release/296/testReport/System.Data.SqlClient.Tests/DiagnosticTest/ExecuteReaderTest/

Message:

Assert.Equal() Failure
        Expected: 402b697d-f354-43b5-8d15-7048ae97092e
        Actual:   f2f6ba90-48ca-4fb2-9572-7d12b0387246

Stack Trace:

/mnt/resource/j/workspace/dotnet_corefx/master/portablelinux_release/src/System.Data.SqlClient/tests/FunctionalTests/DiagnosticTest.cs(460,0): at System.Data.SqlClient.Tests.DiagnosticTest.<>c__DisplayClass27_0.<CollectStatisticsDiagnostics>b__0(KeyValuePair`2 kvp)
           /mnt/resource/j/workspace/dotnet_corefx/master/portablelinux_release/src/System.Diagnostics.DiagnosticSource/src/System/Diagnostics/DiagnosticListener.cs(209,0): at System.Diagnostics.DiagnosticListener.Write(String name, Object value)
           /mnt/resource/j/workspace/dotnet_corefx/master/portablelinux_release/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlClientDiagnosticListenerExtensions.cs(78,0): at System.Data.SqlClient.SqlClientDiagnosticListenerExtensions.WriteCommandAfter(DiagnosticListener this, Guid operationId, SqlCommand sqlCommand, String operation)
           /mnt/resource/j/workspace/dotnet_corefx/master/portablelinux_release/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlCommand.cs(1373,0): at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
           /mnt/resource/j/workspace/dotnet_corefx/master/portablelinux_release/src/System.Data.SqlClient/src/System/Data/SqlClient/SqlCommand.cs(1331,0): at System.Data.SqlClient.SqlCommand.ExecuteReader()

@KristinXie1
Copy link
Author

@saurabh500
Copy link
Contributor

@tstringer all except one failure was the guid mismatch from the diagnostics test.
I have seen the tcp exception and looking into it. Can you diagnose the guid mismatch failure?

@saurabh500
Copy link
Contributor

Since there are multiple listeners beings installed for diagnostics and the tests are executing in parallel, each listener can listen to all commands being executed.
Since the tests are executing in parallel, one of the listeners is getting a notification about the beginning of one of the commands and then the notification for the completion of another command. As a result the Guid retrieved before command execution doesn't match the Guid of the command post execution.

This can be solved by executing the tests in serial instead of parallel.
I have a pull request open dotnet/corefx#15798 where I am trying to make the different DiagnosticsTests not interfere with each other. I will try to complete asap and it should take care of this issue of Guid mismatch as well.

@JonHanna
Copy link
Contributor

https://ci.dot.net/job/dotnet_corefx/job/master/job/osx_release_prtest/3540/ is OS X but seems perhaps a variant of the same

@stephentoub
Copy link
Member

@stephentoub stephentoub self-assigned this Feb 21, 2017
@stephentoub
Copy link
Member

This is causing a bunch of failures. @saurabh500, I know you have a larger set of changes in the works, but I'm going to submit a fix for this particular issue to unblock things.

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.0.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Data.SqlClient test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

No branches or pull requests

8 participants