Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Fix test failure in XmlWriterTraceListenerTests.ListenerWithFilter - #37368

Merged
stephentoub merged 1 commit into
dotnet:masterfrom
stephentoub:textwriterfailure
May 2, 2019
Merged

Fix test failure in XmlWriterTraceListenerTests.ListenerWithFilter#37368
stephentoub merged 1 commit into
dotnet:masterfrom
stephentoub:textwriterfailure

Conversation

@stephentoub

Copy link
Copy Markdown
Member

This test randomly and somewhat amusingly failed in CI. The test validates that a particular value passed into one of the writer's methods doesn't show up in the output, but the writer also outputs the current process ID, and the process ID happened to match that value. The fix is to just ensure it doesn't.

cc: @ViktorHofer, @wtgodbe, @krwq

@stephentoub

Copy link
Copy Markdown
Member Author

@ViktorHofer, lots of PRs (including this one) have been hitting this in the Packaging All Configurations build:

D:\a\1\s\.dotnet\sdk\3.0.100-preview3-010431\NuGet.targets(119,5): error : Failed to retrieve information about 'Microsoft.TargetingPack.Private.NETNative' from remote source 'https://dotnetfeed.blob.core.windows.net/dotnet-core/flatcontainer/microsoft.targetingpack.private.netnative/index.json'. [D:\a\1\s\external\runtime\runtime.depproj]
D:\a\1\s\.dotnet\sdk\3.0.100-preview3-010431\NuGet.targets(119,5): error :   A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [D:\a\1\s\external\runtime\runtime.depproj]
    0 Warning(s)

Do you know what's going on?

@ViktorHofer

Copy link
Copy Markdown
Member

Yes that will be fixed with an updated sdk. Pr is open but we are hitting arcade issues: #37340

Waiting for @tmat to respond.

This test randomly and somewhat amusingly failed in CI.  The test validates that a particular value passed into one of the writer's methods doesn't show up in the output, but the writer also outputs the current process ID, and the process ID happened to match that value.  The fix is to just ensure it doesn't.
@stephentoub
stephentoub force-pushed the textwriterfailure branch from 193ee6f to bf79afa Compare May 2, 2019 16:02
@stephentoub
stephentoub merged commit 541d941 into dotnet:master May 2, 2019
@stephentoub
stephentoub deleted the textwriterfailure branch May 2, 2019 17:17
@karelz karelz added this to the 3.0 milestone May 4, 2019
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…otnet/corefx#37368)

This test randomly and somewhat amusingly failed in CI.  The test validates that a particular value passed into one of the writer's methods doesn't show up in the output, but the writer also outputs the current process ID, and the process ID happened to match that value.  The fix is to just ensure it doesn't.

Commit migrated from dotnet/corefx@541d941
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants