Skip to content

fix(net): exit solidity node block sync on shutdown #650

fix(net): exit solidity node block sync on shutdown

fix(net): exit solidity node block sync on shutdown #650

Triggered via pull request June 2, 2026 09:20
Status Cancelled
Total duration 7m 8s
Artifacts

pr-build.yml

on: pull_request
Build debian11 (JDK 8 / x86_64)
6m 48s
Build debian11 (JDK 8 / x86_64)
Coverage Base (JDK 8 / x86_64)
6m 47s
Coverage Base (JDK 8 / x86_64)
Build ubuntu24 (JDK 17 / aarch64)
6m 58s
Build ubuntu24 (JDK 17 / aarch64)
Build rockylinux (JDK 8 / x86_64)
6m 48s
Build rockylinux (JDK 8 / x86_64)
Matrix: build-macos
Coverage Gate
0s
Coverage Gate
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 5 warnings
Coverage Base (JDK 8 / x86_64)
Canceling since a higher priority waiting request for PR Build-6804 exists
Coverage Base (JDK 8 / x86_64)
The operation was canceled.
Build debian11 (JDK 8 / x86_64)
Canceling since a higher priority waiting request for PR Build-6804 exists
Build debian11 (JDK 8 / x86_64)
The operation was canceled.
Build rockylinux (JDK 8 / x86_64)
Canceling since a higher priority waiting request for PR Build-6804 exists
Build rockylinux (JDK 8 / x86_64)
The operation was canceled.
Build ubuntu24 (JDK 17 / aarch64)
Canceling since a higher priority waiting request for PR Build-6804 exists
Build ubuntu24 (JDK 17 / aarch64)
The operation was canceled.
Build macos26 (JDK 17 / aarch64)
Canceling since a higher priority waiting request for PR Build-6804 exists
Build macos26 (JDK 17 / aarch64)
The operation was canceled.
PR Build
Canceling since a higher priority waiting request for PR Build-6804 exists
Coverage Base (JDK 8 / x86_64)
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 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/
Build debian11 (JDK 8 / x86_64)
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 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/
Build rockylinux (JDK 8 / x86_64)
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 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/
Build ubuntu24 (JDK 17 / aarch64)
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 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/
Build macos26 (JDK 17 / aarch64)
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 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/