Skip to content

Fix hard-coded Hostx64 path to support arm64 and x86 hosts #195

Fix hard-coded Hostx64 path to support arm64 and x86 hosts

Fix hard-coded Hostx64 path to support arm64 and x86 hosts #195

Triggered via pull request April 11, 2026 01:29
Status Failure
Total duration 1m 17s
Artifacts

main.yml

on: pull_request
Matrix: linux
Matrix: macos
Matrix: windows
Fit to window
Zoom out
Zoom in

Annotations

29 errors and 10 warnings
linux (Release)
The strategy configuration was canceled because "linux.Debug" failed
linux (Release)
Process completed with exit code 1.
linux (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Debug)
Process completed with exit code 1.
linux (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
linux (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Release)
Process completed with exit code 1.
macos (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Release): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Debug)
The strategy configuration was canceled because "macos.Release" failed
macos (Debug)
The operation was canceled.
macos (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
macos (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
windows (Debug)
Process completed with exit code 1.
windows (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
windows (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
windows (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
windows (Debug): src/msbuild/DNNE.BuildTasks/Windows.cs#L203
The name 'fallbackHostDirs' does not exist in the current context
windows (Release)
The strategy configuration was canceled because "windows.Debug" failed
windows (Release)
The operation was canceled.
linux (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
linux (Release)
No files were found with the provided path: unittest.Release.binlog. No artifacts will be uploaded.
linux (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
linux (Debug)
No files were found with the provided path: unittest.Debug.binlog. No artifacts will be uploaded.
macos (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macos (Release)
No files were found with the provided path: unittest.Release.binlog. No artifacts will be uploaded.
macos (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows (Debug)
No files were found with the provided path: unittest.Debug.binlog. No artifacts will be uploaded.
windows (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/