[wasm] Debugger tests - fix build #82958
Merged
Conversation
This file contains 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
`/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignment` Started being hit with dotnet#82479 . The other instances of this were fixed in dotnet#82803 .
And this includes the debugger tests
radical
added
arch-wasm
ghost
assigned 
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Started being hit with #82479 .
|
lewing
approved these changes
Mar 3, 2023
thaystg
approved these changes
Mar 3, 2023
|
if this is breaking CI you can merge it before tests complete |
|
The debugger tests built without issues. Merging this to unbreak CI. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignmentStarted being hit with #82479 .
The other instances of this were fixed in #82803 .
Fixes #82962 .