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

Test failures: System.Net.Http.Functional.Tests.DiagnosticsTest / * #24515

Closed
karelz opened this issue Dec 24, 2017 · 2 comments
Closed

Test failures: System.Net.Http.Functional.Tests.DiagnosticsTest / * #24515

karelz opened this issue Dec 24, 2017 · 2 comments
Labels
area-System.Net.Http test-bug Problem in test source code (most likely) test-run-core Test failures in .NET Core test runs
Milestone

Comments

@karelz
Copy link
Member

karelz commented Dec 24, 2017

Types of failures

Affected tests:

  • System.Net.Http.Functional.Tests.DiagnosticsTest:
    • SendAsync_ExpectedDiagnosticSourceLogging
    • SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
    • SendAsync_ExpectedDiagnosticSourceUrlFilteredActivityLogging
    • SendAsync_ExpectedDiagnosticStopOnlyActivityLogging
  • System.Net.Http.Functional.Tests.HttpClientHandler_DefaultProxyCredentials_Test:
    • ProxySetViaEnvironmentVariable_DefaultProxyCredentialsUsed

Test SendAsync_ExpectedDiagnosticStopOnlyActivityLogging

Exit code was 139 but it should have been 42
Expected: True
Actual:   False
at System.Diagnostics.RemoteExecutorTestBase.RemoteInvokeHandle.Dispose() in /root/corefx-1192569/src/CoreFx.Private.TestUtilities/src/System/Diagnostics/RemoteExecutorTestBase.cs:line 203
at System.Net.Http.Functional.Tests.DiagnosticsTest.SendAsync_ExpectedDiagnosticStopOnlyActivityLogging() in /root/corefx-1192569/src/System.Net.Http/tests/FunctionalTests/DiagnosticsTests.cs:line 583

History of failures

Day Build OS Test
5/31 2017053.01 Ubuntu16.04 SendAsync_ExpectedDiagnosticSourceLogging
7/8 20170708.04 Suse42.2 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
8/1 20170801.01 Ubuntu17.04 SendAsync_ExpectedDiagnosticSourceUrlFilteredActivityLogging
8/19 20170819.02 Ubuntu17.04 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
8/22 20170822.01 Centos73 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceUrlFilteredActivityLogging
8/23 20170823.07 Ubuntu17.04 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
8/27 20170827.01 Centos73 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
9/25 20170925.03 Ubuntu17.04 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceUrlFilteredActivityLogging
9/26 20170926.06 RedHat72 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceLogging
9/26 20170926.06 RedHat72 [ManagedHandler] SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
10/1 20171001.01 RedHat72 [ManagedHandler] ProxySetViaEnvironmentVariable_DefaultProxyCredentialsUsed
10/26 20171026.01 Suse42.2 ProxySetViaEnvironmentVariable_DefaultProxyCredentialsUsed
11/18 20171118.03 Ubuntu17.10 SendAsync_ExpectedDiagnosticSourceLogging
11/27 20171127.01 Ubuntu16.04 SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
12/4 20171204.02 Ubuntu17.04 SendAsync_ExpectedDiagnosticStopOnlyActivityLogging
12/23 20171223.03 Ubuntu17.04 SendAsync_ExpectedDiagnosticSourceNewAndDeprecatedEventsLogging
1/12 20180112.01 Ubuntu14.04 SendAsync_ExpectedDiagnosticStopOnlyActivityLogging - link
1/19 20180119.01 Suse42.4 ProxySetViaEnvironmentVariable_DefaultProxyCredentialsUsed - link
3/31 20180331.02 Ubuntu16.04 SendAsync_ExpectedDiagnosticSourceLogging
3/31 20180331.05 OpenSuse42.3 SendAsync_ExpectedDiagnosticSourceLogging

Note: Related to:

@karelz karelz changed the title Test failures: Diagnostics tests Test failures: System.Net.Http.Functional.Tests.DiagnosticsTest / * Dec 24, 2017
@karelz
Copy link
Member Author

karelz commented Dec 29, 2017

Analysis from @vancem in duplicate bug: https://github.com/dotnet/corefx/issues/24807#issuecomment-348545336

I am assuming that this is a non-deterministic (and rare) error. Please correct me if I am wrong.
Looking at the error detail

2:14:30   xUnit.net console test runner (64-bit .NET Core)
12:14:30   Copyright (C) 2014 Outercurve Foundation.
12:14:30   
12:14:30   Discovering: System.Net.Mail.Functional.Tests
12:14:31   Discovered:  System.Net.Mail.Functional.Tests
12:14:31   Starting:    System.Net.Mail.Functional.Tests
12:14:32 
  A fatal error occurred, the required library libhostfxr.dylib could not be found at /Users/dotnet-bot/j/workspace/dotnet_corefx/master/outerloop_netcoreapp_osx_release/bin/testhost/netcoreapp-OSX-Release-x64/shared/Microsoft.NETCore.App/9.9.9/
12:14:33 
     System.Net.Mail.Tests.LoggingTest.EventSource_EventsRaisedAsExpected [FAIL]
12:14:33         Exit code was 131 but it should have been 42
12:14:33         Expected: True
12:14:33         Actual:   False
12:14:33         Stack Trace:
12:14:33            /Users/dotnet-bot/j/workspace/dotnet_corefx/master/outerloop_netcoreapp_osx_release/src/CoreFx.Private.TestUtilities/src/System/Diagnostics/RemoteExecutorTestBase.cs(203,0): at System.Diagnostics.RemoteExecutorTestBase.RemoteInvokeHandle.Dispose()
12:14:35   Finished:    System.Net.Mail.Functional.Tests

This seems to be some sort loader issue with libhostfxr.dylib which I am guessing is something to do with the test host.
We probably need to bring in some expertise with this DLL and how it is deployed. It seems to have little to do with the actual code being tested.

@davidsh
Copy link
Contributor

davidsh commented Apr 29, 2019

These tests have been active for a while now and no failures reported.

@davidsh davidsh closed this as completed Apr 29, 2019
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 3.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Http test-bug Problem in test source code (most likely) test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

No branches or pull requests

3 participants