From 8a1da492f4ab9fe912019d0fa8f603d134ec5149 Mon Sep 17 00:00:00 2001 From: Larry Ewing Date: Wed, 9 Sep 2026 17:41:03 -0500 Subject: [PATCH] Make browser WASM R2R tests blocking Remove the temporary continue-on-error configuration and use the shared Helix job monitor now that the restored lane is clean. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- eng/pipelines/runtime.yml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/eng/pipelines/runtime.yml b/eng/pipelines/runtime.yml index a2d43e6992d2e2..e58e2d50c0b2af 100644 --- a/eng/pipelines/runtime.yml +++ b/eng/pipelines/runtime.yml @@ -1965,9 +1965,6 @@ extends: - browser_wasm helixQueueGroup: pr helixQueuesTemplate: /eng/pipelines/coreclr/templates/helix-queues-setup.yml - # Keep known failures visible without blocking the runtime pipeline. - # Tracked by https://github.com/dotnet/runtime/issues/133305. - shouldContinueOnError: true jobParameters: testGroup: innerloop readyToRun: true @@ -1975,8 +1972,7 @@ extends: liveLibrariesBuildConfig: Release unifiedArtifactsName: CoreCLR_ReleaseLibraries_BuildArtifacts_$(osGroup)$(osSubgroup)_$(archType)_$(_hostedOs)_$(_BuildConfig) unifiedBuildNameSuffix: CoreCLR_ReleaseLibraries - # The shared monitor would turn this non-blocking lane into a pipeline failure. - useHelixMonitor: false + useHelixMonitor: ${{ variables.enableHelixJobMonitor }} extraBuildArgs: -os browser -p:HostConfiguration=Release condition: >- or(