-
Notifications
You must be signed in to change notification settings - Fork 188
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
fix: Conditional access mutations could lead to unrecoverable NullReferenceException in compilation #2888
Conversation
2a31da4
to
4a2642f
Compare
I've tested this and it seems to work :) But I'm still seeing some error logging:
When was this added? And should we fix these in this PR? Or can we fix this later |
Thanks for reporting.
This is not new, there was several way for mutations to be silently loss along the way. My last refactoring made the process more trustworthy.
I think I added this in my refactor PR while analyzing some strange issues. At first I assumed there was a problem copying the mutated assembly, but it turned out to be that Stryker was running unrelated test Will fix in this PR |
Continuing comment:
So these are triggered by the mutated assembly not being tested by any test. It can happen with solution mode due to the support for transitive testing. In Stryker's case, these are triggered by Stryker.RegexMutators. ==> I downgraded severity down to Debug and stressed the lack of testing as the probable cause |
@richardwerkman : it should be ok now, could please check it again and confirm on your side? |
6fca491
to
45cc7ac
Compare
45cc7ac
to
c976a29
Compare
Quality Gate failedFailed conditions |
@dupdob thanks for the quick fix! Great work 👍 |
your feedback is welcomed 😄 |
Fix issues related to Conditional Access (and NullSuppression operator)
Add recovery mechanism for when the compilation triggers null reference exception
Fix #2880