-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[9.0-preview.2] Inconsistent messaging of success vs. warnings from dotnet test #39665
Comments
The CI vs. not thing might actually be a different issue. Carrying on with what I was actually doing when I observed the original issue, I find that in CI the tests failing isn't being reported on the console - I just get I can only see why the tests failed with the GitHub Actions test logger. |
I will fix net9 output when all tests are skipped to say Skipped! rather than Passed!. The CI output is interesting, you are using the preview2 version which should print errors via msbuild api, so they should show up on console, maybe it is the extra logger the action is providing, but it seems unlikely. Most of my updates on terminal logger integration go here: microsoft/vstest#4843 |
I've re-read this again, and looked at terminal logger code, and I think it will be for the best if the test summary in terminal logger does not report success or fail, but instead just says: |
Observing this still with preview.3 - here's an example. |
We couldn't get this into the preview 3 cutoff, but the PR is undergoing approvals and should be in preview 4. |
Describe the bug
When tests are intentionally skipped, the .NET SDK reports inconsistent messaging on whether the build/tests succeeded. This behaviour also varies between running locally and in GitHub Actions (interactive vs. not).
.NET 8
.NET 9 in CI
.NET 9 Locally
In CI there's no detail of the skipped tests (or indeed that any tests were even run).
Locally, the messaging is inconsistent (emphasis mine):
The messaging suggests that build and test both succeeded and succeeded with warning.
Based on my intent at least, in this scenario I would expect the build and the tests to both be successful because no tests failed.
If regardless of my intent skipping should be treated as a warning, then then messaging should be consistent and arguably it should be possible to treat skipped tests as not being at a warning level.
To Reproduce
build.ps1
from the root of the repository.Further technical details
.NET SDK
9.0.100-preview.2.24157.14
/cc @nohwnd
The text was updated successfully, but these errors were encountered: