Temporary workaround for unstable SA1134 code fix#3714
Closed
bjornhellander wants to merge 1 commit intoDotNetAnalyzers:masterfrom
Closed
Temporary workaround for unstable SA1134 code fix#3714bjornhellander wants to merge 1 commit intoDotNetAnalyzers:masterfrom
bjornhellander wants to merge 1 commit intoDotNetAnalyzers:masterfrom
Conversation
…ber of iterations in one specific test case DotNetAnalyzers#2438
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #3714 +/- ##
=======================================
Coverage 93.12% 93.13%
=======================================
Files 1088 1088
Lines 115029 115037 +8
Branches 4113 4113
=======================================
+ Hits 107126 107134 +8
Misses 6862 6862
Partials 1041 1041 |
Member
|
I'm planning to take #2853 instead of this one |
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
2 participants
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.
Would this be ok to get rid on random failures of the test VerifyMultipleAttributesOnSameLineForMembersAsync?
This happens quite often unfortunately. Unsure if this helps, but I interpret the documentation like it should.