Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved by danmoseley · Pull Request #126012 · dotnet/runtime

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-24T04:00:12Z

Note

This PR was generated with the help of GitHub Copilot.

Set MSBUILDDEBUGPATH in CI so MSBuild crash diagnostics are preserved in more build types.

When MSBuild worker nodes crash during CI builds (see #92290), diagnostic MSBuild_*.failure.txt files are written to a system temp directory on the ephemeral build agent and lost when the agent is cleaned up. This makes it impossible to determine the root cause of the crashes.

Several component-specific build scripts (src/coreclr/build-runtime.sh, src/tests/build.sh, src/native/corehost/build.sh) already set MSBUILDDEBUGPATH to artifacts/log/<config>/MsbuildDebugLogs, but the top-level build invoked by the pipeline template (global-build-step.yml) does not. Build legs that don't go through one of those component scripts — such as the macOS libs/mono builds currently hitting #92290 — get the default temp dir.

This adds MSBUILDDEBUGPATH as a job-level pipeline variable in global-build-job.yml, pointing to the same artifacts/log/<config>/MsbuildDebugLogs path. The existing condition: always() log publishing step in job.yml already sweeps artifacts/log/, so the failure diagnostics will be automatically published as build artifacts the next time a crash occurs.

When MSBuild worker nodes crash during builds (dotnet#92290), diagnostic failure.txt files are written to a system temp directory on the ephemeral agent and lost. This sets MSBUILDDEBUGPATH to a path under artifacts/log/ so the existing always-on log publishing step picks them up automatically. The coreclr build scripts already set this for their specific build steps, but this covers all build legs including the macOS libs/mono builds that are currently hitting the issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

dotnet-policy-service · 2026-03-24T04:02:03Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the CI global build job template to set MSBUILDDEBUGPATH so MSBuild crash diagnostics (e.g., MSBuild_*.failure.txt) are written under artifacts/log/... and can be published with build logs instead of being lost in ephemeral agent temp directories.

Changes:

Add a job-level MSBUILDDEBUGPATH pipeline variable in the global build job template.
Point MSBUILDDEBUGPATH at artifacts/log/<config>/MsbuildDebugLogs to align with existing log publishing.

danmoseley · 2026-03-25T00:56:14Z

@copilot handle feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

danmoseley · 2026-03-26T03:09:15Z

/ba-g unrelated build timeout

danmoseley · 2026-03-26T13:55:58Z

/ba-g build timeout

…rash diagnostics The MSBUILDDEBUGPATH pipeline variable added in PR dotnet#126012 is not reaching the MSBuild process during Build product steps. Set the env var directly in the build scripts, matching the existing pattern in build-runtime.sh and tests/build.sh. Also create the directory with mkdir -p / New-Item -Force to avoid issues with MSBuild's EnsureDirectoryExists (which has no try/catch in its static constructor). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

CopilotAI review requested due to automatic review settings March 24, 2026 04:00

github-actionsBot added the area-Build-mono label Mar 24, 2026

dotnet-policy-serviceBot assigned danmoseley Mar 24, 2026

Copilotstarted reviewing on behalf of danmoseley March 24, 2026 04:01 View session

danmoseley added area-Infrastructure and removed area-Build-mono labels Mar 24, 2026

github-project-automationBot added this to Runtime Infra Mar 24, 2026

CopilotAI reviewed Mar 24, 2026
View reviewed changes

Comment threadeng/pipelines/common/global-build-job.yml Outdated

Use _BuildConfig for correct casing on case-sensitive filesystems
3705072
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This was referenced Mar 25, 2026
Cannot find 'arm64-v8a' device dotnet/dnceng#2284
Closed
[Android][CoreCLR] System.Security.Cryptography.Tests killed by lowmemorykiller #118603
Open
Timeout running System.Data.OleDb.Tests #126067
Open

hoyosjs approved these changes Mar 26, 2026
View reviewed changes

danmoseley enabled auto-merge (squash) March 26, 2026 13:54

danmoseley merged commit 116bd0d into dotnet:mainMar 26, 2026
164 of 172 checks passed

github-project-automationBot moved this to Done in Runtime Infra Mar 26, 2026

dotnet-maestroBot mentioned this pull request Mar 27, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#5738
Merged

danmoseley deleted the msbuild-debugpath-ci branch March 27, 2026 03:36

danmoseley mentioned this pull request Apr 12, 2026
Set MSBUILDDEBUGPATH in build scripts for reliable crash diagnostics #126806
Closed

github-actionsBot locked and limited conversation to collaborators Apr 26, 2026