chore: avoid analyzer test Buildalyzer hang#1798
Merged
martinothamar merged 1 commit intoJun 5, 2026
Merged
Conversation
Contributor
📝 WalkthroughWalkthroughThe PR refactors ChangesSimplified fixture initialization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
martinothamar
approved these changes
Jun 5, 2026
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.
Summary
Why
The local analyzer test harness could hang inside Buildalyzer/MSBuild pipe logger disposal when the fixture forced a non-design-time
Clean;Build. The analyzer tests only need Roslyn compilation inputs, not build outputs, so design-time analysis is a better fit.Testing
dotnet build test/Altinn.App.Analyzers.Tests/Altinn.App.Analyzers.Tests.csproj -v minimaltimeout 120s dotnet test test/Altinn.App.Analyzers.Tests/Altinn.App.Analyzers.Tests.csproj --no-build -v normal --filter "FullyQualifiedName~HttpContextAccessorUsageAnalyzerTests.Emits_Diagnostic" --blame-hang --blame-hang-timeout 2m --blame-hang-dump-type minidotnet test test/Altinn.App.Analyzers.Tests/Altinn.App.Analyzers.Tests.csproj --no-build -v minimal --filter "Category!=Integration"Build emits existing NU1903 package vulnerability warnings for Microsoft.Build/System.Security.Cryptography.Xml packages.
Summary by CodeRabbit
Release Notes
This pull request contains internal testing infrastructure improvements with no user-facing changes. Updates include: