Add VS feedback tool integration for MIEngine diagnostic logs #2387
WardenGnawBuild-And-Test.yml
on: pull_request
windows_vscode_build
6m 43s
linux_build
2m 23s
osx_build
35s
Matrix: windows_vs_build
Annotations
56 warnings
|
osx_build
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/
|
|
osx_build
No files were found with the provided path: /Users/runner/work/MIEngine/MIEngine/bin/DebugAdapterProtocolTests/Debug/CppTests/results.trx. No artifacts will be uploaded.
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L296
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L258
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L229
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L183
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L166
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L124
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L109
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L70
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L51
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
osx_build:
test/DebuggerTesting/OpenDebug/Events/StoppedEvent.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build
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_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L124
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L109
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L296
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L258
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L229
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L183
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L166
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L70
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/CppTests/OpenDebug/CrossPlatCpp/InspectorValueExtensions.cs#L51
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
linux_build:
test/DebuggerTesting/OpenDebug/Events/StoppedEvent.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (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, darenm/Setup-VSTest@v1.3, microsoft/setup-msbuild@v2, NuGet/setup-nuget@v2. 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_vs_build (Release):
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L186
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/AndroidLauncherTests.cs#L136
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/CommandLockTests.cs#L166
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/AndroidLauncherTests.cs#L58
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/CommandLockTests.cs#L143
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/CommandLockTests.cs#L92
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/CommandLockTests.cs#L80
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Release):
src/MICoreUnitTests/CommandLockTests.cs#L26
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Release):
src/DebugEngineHost.Stub/DebugEngineHost.ref.cs#L312
Missing XML comment for publicly visible type or member 'HostLogger.WriteFeedbackLog(string)'
|
|
windows_vs_build (Release):
src/DebugEngineHost/HostOutputWindow.cs#L72
Await/join tasks created from ThreadHelper.JoinableTaskFactory.RunAsync (https://github.com/Microsoft/VSSDK-Analyzers/blob/main/doc/VSSDK007.md)
|
|
windows_vs_build (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, darenm/Setup-VSTest@v1.3, microsoft/setup-msbuild@v2, NuGet/setup-nuget@v2. 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_vs_build (Debug):
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L186
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/AndroidLauncherTests.cs#L136
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/CommandLockTests.cs#L166
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/CommandLockTests.cs#L143
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/CommandLockTests.cs#L92
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/CommandLockTests.cs#L80
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/AndroidLauncherTests.cs#L58
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vs_build (Debug):
src/MICoreUnitTests/CommandLockTests.cs#L26
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vs_build (Debug):
src/DebugEngineHost.Stub/DebugEngineHost.ref.cs#L312
Missing XML comment for publicly visible type or member 'HostLogger.WriteFeedbackLog(string)'
|
|
windows_vs_build (Debug):
src/DebugEngineHost/HostOutputWindow.cs#L72
Await/join tasks created from ThreadHelper.JoinableTaskFactory.RunAsync (https://github.com/Microsoft/VSSDK-Analyzers/blob/main/doc/VSSDK007.md)
|
|
windows_vscode_build
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, microsoft/setup-msbuild@v2, NuGet/setup-nuget@v2. 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_vscode_build:
src/MICoreUnitTests/CommandLockTests.cs#L143
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vscode_build:
src/MICoreUnitTests/CommandLockTests.cs#L80
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
windows_vscode_build:
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L244
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L220
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L186
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/MICoreUnitTests/BasicLaunchOptionsTests.cs#L203
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/MICoreUnitTests/AndroidLauncherTests.cs#L136
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/MICoreUnitTests/AndroidLauncherTests.cs#L58
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|
|
windows_vscode_build:
src/DebugEngineHost.Stub/DebugEngineHost.ref.cs#L312
Missing XML comment for publicly visible type or member 'HostLogger.WriteFeedbackLog(string)'
|
|
windows_vscode_build:
src/DebugEngineHost/HostOutputWindow.cs#L72
Await/join tasks created from ThreadHelper.JoinableTaskFactory.RunAsync (https://github.com/Microsoft/VSSDK-Analyzers/blob/main/doc/VSSDK007.md)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
linux_x64_results
|
755 KB |
sha256:9a350059a2bfc44c1dec38a678da1e2361fd00cae3a7071e1aedcf369bdf72ab
|
|
|
win_msys2_x64_results
|
1.04 MB |
sha256:0ba5cfb7b263e06e24452ee7012c67c4244d915cfe46dbb831f4786947a98ad5
|
|