Skip to content

V10.1.4/service update #29

V10.1.4/service update

V10.1.4/service update #29

Triggered via pull request June 5, 2026 21:45
Status Failure
Total duration 5m 54s
Artifacts 18

ci-pipeline.yml

on: pull_request
initialize
2s
initialize
Matrix: call-build
Matrix: call-pack
Matrix: call-test-linux
Matrix: call-test-windows
Matrix: call-test-mac
Waiting for pending jobs
test-qualitygate
4s
test-qualitygate
call-codecov  /  📊 Code Coverage Analysis
call-codecov / 📊 Code Coverage Analysis
call-codeql  /  🛡️ Security Analysis
call-codeql / 🛡️ Security Analysis
call-sonarcloud  /  🔬 Code Quality Analysis
call-sonarcloud / 🔬 Code Quality Analysis
call-nuget  /  deploy
call-nuget / deploy
call-nuget  /  deploy_environment
call-nuget / deploy_environment
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 18 warnings, and 2 notices
Failed test: Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver
Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver Message: Assert.True() Failure Expected: True Actual: False Stack trace: at Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver() in /_/test/Codebelt.Extensions.Newtonsoft.Json.Tests/DynamicContractResolverTest.cs:line 51 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
call-test-linux (X64, Release) / 🧪 Test
Process completed with exit code 1.
Failed test: Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver
Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver Message: Assert.True() Failure Expected: True Actual: False Stack trace: at Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver() in /_/test/Codebelt.Extensions.Newtonsoft.Json.Tests/DynamicContractResolverTest.cs:line 51 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
call-test-linux (ARM64, Release) / 🧪 Test
Process completed with exit code 1.
Failed test: Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver
Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver Message: Assert.True() Failure Expected: True Actual: False Stack trace: at Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver() in /_/test/Codebelt.Extensions.Newtonsoft.Json.Tests/DynamicContractResolverTest.cs:line 51 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
call-test-windows (X64, Release) / 🧪 Test
Process completed with exit code 1.
Failed test: Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver
Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver Message: Assert.True() Failure Expected: True Actual: False Stack trace: at Codebelt.Extensions.Newtonsoft.Json.DynamicContractResolverTest.Create_WithHandlers_ShouldApplyHandlersForCamelCaseResolver() in /_/test/Codebelt.Extensions.Newtonsoft.Json.Tests/DynamicContractResolverTest.cs:line 51 at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
call-test-windows (ARM64, Debug) / 🧪 Test
Process completed with exit code 1.
test-qualitygate
Process completed with exit code 1.
test-qualitygate
test_linux finished with 'failure'.
call-build (Release, X64) / 🛠️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-build (Release, ARM64) / 🛠️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-build (Debug, X64) / 🛠️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-build (Debug, ARM64) / 🛠️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-pack (Debug) / 📦 Pack
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-pack (Release) / 📦 Pack
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-linux (X64, Release) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-linux (X64, Release) / 🧪 Test
No files were found with the provided path: /home/runner/work/newtonsoft-json/newtonsoft-json/Coverage. No artifacts will be uploaded.
call-test-linux (X64, Debug) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-linux (ARM64, Release) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-linux (ARM64, Release) / 🧪 Test
No files were found with the provided path: /home/runner/work/newtonsoft-json/newtonsoft-json/Coverage. No artifacts will be uploaded.
call-test-linux (ARM64, Debug) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-windows (X64, Debug) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-windows (X64, Release) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-windows (X64, Release) / 🧪 Test
No files were found with the provided path: D:\a\newtonsoft-json\newtonsoft-json/Coverage. No artifacts will be uploaded.
call-test-windows (ARM64, Debug) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-windows (ARM64, Debug) / 🧪 Test
No files were found with the provided path: C:\a\newtonsoft-json\newtonsoft-json/Coverage. No artifacts will be uploaded.
call-test-windows (ARM64, Release) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
call-test-windows (X64, Debug) / 🧪 Test
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
call-test-windows (X64, Release) / 🧪 Test
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
CoverageReport-Debug-Linux-ARM64-
1.36 MB
sha256:6681a699ced7b673b764ac703c7c3b94d718c40622557bca44a107f1f9b6deda
CoverageReport-Debug-Linux-X64-
1.36 MB
sha256:72a35b883aed671d106e588c9f5d435beb3677715a48812b651f02b9244fc323
CoverageReport-Debug-Windows-X64-
1.36 MB
sha256:8bb9955106acd74bd6db9b04162168cfc6a2a028c07c289613eb3c3a917de987
CoverageReport-Release-Windows-ARM64-
1.36 MB
sha256:4df8afee3d4c67c61b75df4090711f7538a2bbe50dcdec1bc80c579f5030490f
NuGet-Debug
219 KB
sha256:467d649ddc71ccf8a1efbb8c9ea7d2f7a6b81ec785623f582b18f8703298595f
NuGet-Release
211 KB
sha256:a5f54a979422cc19cf99da5ebcd9876402ffd34b52b0ebbcb5edb3186a060fd6
TestResults-Debug-Linux-ARM64-
309 KB
sha256:6829b5c7d9d3c2e0cd54a58e541948e5cc9a42ea2dc27ad60ad0dc2f708dfe5f
TestResults-Debug-Linux-X64-
310 KB
sha256:428867338feaa62f870d7d087dfb13371e1fd0cbedee4ea47a32221117bd9a44
TestResults-Debug-Windows-ARM64-
334 KB
sha256:35f8c2f2a93028ab6ca5c5de114b796a266b3c4fcbe2b12a4bcc554d0832a75b
TestResults-Debug-Windows-X64-
333 KB
sha256:cd51018d99295999ee5724322a4d0ce4dda52483c43525dc875ac6e16f4a9ffe
TestResults-Release-Linux-ARM64-
276 KB
sha256:9ed7780918d784671af5b9a13cfae04ddca49195390fd320b3d8e17495e84481
TestResults-Release-Linux-X64-
277 KB
sha256:93fa88a65a1a3f2d9c420d6e4de74b57e996e8dea1deea61c5fe2df8c3668976
TestResults-Release-Windows-ARM64-
300 KB
sha256:098fd6728b7fea240e6f70b53f09533c2395013a8c10b388738a3526c14c32e0
TestResults-Release-Windows-X64-
300 KB
sha256:ecc7c331a0222207f6b57e456faf1571ccde4614b212b70c5dc3eaf2b8529fe1
build-Debug-ARM64
33.4 MB
sha256:6bc7322eab92ab6d3a8945170ef82c2df15d64d18953bee846c27c0d8ce12759
build-Debug-X64
33.4 MB
sha256:5f9561c2dae0ff6c0c2c1703b0d8635eb5f6d4a03864dbad764d309ec6bff8cd
build-Release-ARM64
33.3 MB
sha256:99ae13246c3cb94f0071738b057bd951886922a24631516b04033433687b88b6
build-Release-X64
33.3 MB
sha256:25037dc2c15540c8fdf93e255931c095e8e456a5a0faf2c560ad0219f1e9230e