Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

LegalFilePathsOnly_rejects_arguments_containing_invalid_path_characters failing after update to .NET SDK RC1 #108

Open
tmat opened this issue May 3, 2018 · 1 comment

Comments

@tmat
Copy link
Member

tmat commented May 3, 2018

https://ci.dot.net/job/dotnet_CliCommandLineParser/job/release_2.1.3xx/job/debug_windows_nt_x64_prtest/17/artifact/artifacts/Debug/TestResults/Microsoft.DotNet.Cli.CommandLine.Tests_netcoreapp2.0_x64.log

      Expected collection {empty} to be equivalent to {"|||"}, but it misses {"|||"}.
      Stack Trace:
        C:\projects\fluentassertions-vf06b\Src\FluentAssertions.Net45\Execution\XUnit2TestFramework.cs(32,0): at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
        C:\projects\fluentassertions-vf06b\Src\Core\Execution\AssertionScope.cs(197,0): at FluentAssertions.Execution.AssertionScope.FailWith(String message, Object[] args)
        C:\projects\fluentassertions-vf06b\Src\Core\Collections\CollectionAssertions.cs(364,0): at FluentAssertions.Collections.CollectionAssertions`2.BeEquivalentTo[T](IEnumerable`1 expected, String because, Object[] becauseArgs)
        C:\projects\fluentassertions-vf06b\Src\Core\Collections\StringCollectionAssertions.cs(41,0): at FluentAssertions.Collections.StringCollectionAssertions.BeEquivalentTo(String[] elements)
        /_/src/tests/CommandLine.Tests/ParsingValidationTests.cs(116,0): at Microsoft.DotNet.Cli.CommandLine.Tests.ParsingValidationTests.LegalFilePathsOnly_rejects_arguments_containing_invalid_path_characters()
      Output:
        124
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

The test is now skipped.

@tmat
Copy link
Member Author

tmat commented May 3, 2018

@livarcocc FYI

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant