Repository navigation
.NET rules for analyzer, format, test-host, audit and platform failures (#62) - #71
Merged
Merged
Conversation
…es (#62) dotnet-analyzer-error, dotnet-format-verify, vstest-testhost-crashed, vstest-blame-hang, nuget-audit-vulnerability, netsdk1100-windows-targeting and msbuild-file-locked, each with a fixture. A TRX whose run aborted now yields a "Test run aborted" failure from its error RunInfo, which report mode used to read as passing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md # CONTRIBUTING.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #62.
csc-compile-errormatchederror CS\d+only, so an analyzer or style diagnostic raised to an error fell through to a generic rule or to "No known rule matched". Those are among the commonest .NET CI failures. Seven rules indotnet.yaml, each with a fixture and a winning-rule row:dotnet-analyzer-errorerror (CA|IDE|SA|RS|RCS|VSTHRD|xUnit|MSTEST|NUnit)\d+: …dotnet-format-verifyerror WHITESPACE|CHARSET|FINALNEWLINE|ENDOFLINE|IMPORTS: …vstest-testhost-crashedThe active test run was aborted. Reason: …,Test host process crashed,Test Run Aborted.vstest-blame-hangThe specified inactivity time of … has elapsed(outranks the crash rule, since a hang also ends "aborted")nuget-audit-vulnerabilityerror NU1901-NU1904: Package 'X' 1.2.3 has a known high severity vulnerability. Errors only: NuGetAudit warns by default, and a warning next to the real failure isn't the cause. A test pins that.netsdk1100-windows-targetingerror NETSDK1100msbuild-file-lockederror MSB3027/MSB3021Fix texts name the concrete remedy: the
.editorconfigseverity key anddotnet format;--blame-crashand--blame-hang-timeout;dotnet list package --vulnerableandNuGetAuditSuppress;EnableWindowsTargeting;dotnet build-server shutdown.Also, TRX: a crashed test host leaves no
Failedresult, only anoutcome="Error"entry underRunInfos, so report mode read the run as passing. That entry is now a failure named "Test run aborted", which the new test-host rules then explain. AWarningrun info is ignored. The parser test covers both.dotnet formatis now a .NET ecosystem marker, so a format log is analysed with the dotnet pack.cifail rules validate: 151 rules, 0 errors, 0 warnings. Core passes 554/554 and Cli 204/204.🤖 Generated with Claude Code