Uh oh!
There was an error while loading. Please reload this page.
[browser][CoreCLR] Gate remaining priority-1 outerloop failures - #131957
Merged
radekdoulik merged 2 commits intoAug 19, 2026
Conversation
Keep b65423's Environment.Exit coverage intact and skip it on CoreCLR browser while the corerun exit path is tracked separately. Restore the fieldlayout Crossgen2 bypass because its R2R assertion occurs before the managed ActiveIssue can run. Gate the unsupported self-process EventPipe tests and temporarily suppress the ContextualReflection interpreter failure. Clarify that Server GC is disabled on CoreCLR browser by design. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 808c6867-a1ea-4256-a003-46c17785ad04
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
radekdoulik
commented
Aug 6, 2026
MemberAuthor
/azp run runtime-coreclr outerloop |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Contributor
Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara |
Contributor
There was a problem hiding this comment.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Note
This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.
Copilot stopped reviewing on behalf of radekdoulik due to an error
August 6, 2026 18:16
pavelsavara
approved these changes
Aug 7, 2026
Remove the b65423 and fieldlayout suppressions now that dotnet#132078 and dotnet#132172 fix their underlying CoreCLR browser failures. Retain the EventPipe, ContextualReflection, and Server GC exclusions that remain necessary on current main. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 808c6867-a1ea-4256-a003-46c17785ad04
radekdoulik
commented
Aug 18, 2026
MemberAuthor
/azp run runtime-coreclr outerloop |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
radekdoulik
commented
Aug 19, 2026
MemberAuthor
/ba-g the PAL tests failures are unrelated |
akoeplinger
approved these changes
Aug 19, 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 freeto 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
Process.GetCurrentProcessand Process/PID-based managed self-processDiagnosticsClientcollection; browser diagnostics use JS/WebSocket clients instead.ContextualReflectioninterpreter failure through its tracked Assert failure: !"OBJECTREF being accessed while thread is in preemptive GC mode." #131925 ActiveIssue.b65423andreadytorun/fieldlayoutare absent from this change: current main includes the underlying fixes from [browser][coreCLR] corerun: hard-exit Node on explicit process exit (#131937) #132078 and Fix WASM R2R virtual IP initialization #132172, and both restored tests now pass targeted browser validation.Related issues: #131321, #131898, #131925.
Validation
origin/mainat663c457b86ccd35743374676a69de5ed97bc3b14; the Checked browserclr+libsbaseline passed with 0 warnings and 0 errors.b65423passed 3/3: browser default, browserDOTNET_TieredCompilation=0, and native macOS arm64 process-isolated execution, each with expected/actual exit code 100.fieldlayoutpassed 2/2 in browser default and no-tiered modes after producing and loading its composite Crossgen2/R2R WASM image.GCEventsrun reproduced the expectedProcess.GetCurrentProcessPlatformNotSupportedException; all four final EventPipe projects were gated from CoreCLR-browser builds.git diff --check origin/main..HEADpassed.Note
This pull request description was generated by GitHub Copilot.