We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
vstest console logger has a hardcoded path separator for the source:
vstest
vstest/src/vstest.console/Internal/ConsoleLogger.cs
Line 744 in f67ad49
./Test.ps -Build
On Linux, Windows and MacOS, the output should be the same:
Passed! - Failed: 0, Passed: 20, Skipped: 0, Total: 20, Duration: 77 ms - AppBrix.Tests.dll (net6.0)
On Linux and MacOS, the output contains the full path to the test assembly:
Passed! - Failed: 0, Passed: 20, Skipped: 0, Total: 20, Duration: 100 ms - /home/runner/work/AppBrix/AppBrix/Tests/AppBrix.Tests/bin/Release/net6.0/AppBrix.Tests.dll (net6.0)
The issue will probably be reproduced if Windows is set to use a different path separator.
Not necessary.
I am running this GitHub action, which is using ubuntu-latest, windows-latest and macOS-latest with dotnet-version: 6.0.x
ubuntu-latest
windows-latest
macOS-latest
dotnet-version: 6.0.x
The text was updated successfully, but these errors were encountered:
Thank you for reporting this @MarinAtanasov. I confirm that I can reproduce the issue:
Passed! - Failed: 0, Passed: 120, Skipped: 0, Total: 120, Duration: 51 ms - /home/amaury/src/AppBrix/Tests/AppBrix.Permissions.Tests/bin/Debug/net6.0/AppBrix.Permissions.Tests.dll (net6.0)
Sorry, something went wrong.
Evangelink
Successfully merging a pull request may close this issue.
Description
vstest
console logger has a hardcoded path separator for the source:vstest/src/vstest.console/Internal/ConsoleLogger.cs
Line 744 in f67ad49
Steps to reproduce
./Test.ps -Build
Expected behavior
On Linux, Windows and MacOS, the output should be the same:
Actual behavior
On Linux and MacOS, the output contains the full path to the test assembly:
The issue will probably be reproduced if Windows is set to use a different path separator.
Diagnostic logs
Not necessary.
Environment
I am running this GitHub action, which is using
ubuntu-latest
,windows-latest
andmacOS-latest
withdotnet-version: 6.0.x
The text was updated successfully, but these errors were encountered: