Skip to content

refactor(vm): optimize opcode energy cost calculation with BigInteger #17

refactor(vm): optimize opcode energy cost calculation with BigInteger

refactor(vm): optimize opcode energy cost calculation with BigInteger #17

Re-run triggered April 9, 2026 07:36
Status Cancelled
Total duration 8m 8s
Artifacts

pr-build.yml

on: pull_request
Build ubuntu24 (JDK 17 / aarch64)
24m 14s
Build ubuntu24 (JDK 17 / aarch64)
Build rockylinux (JDK 8 / x86_64)
8m 1s
Build rockylinux (JDK 8 / x86_64)
Build debian11 (JDK 8 / x86_64)
19m 30s
Build debian11 (JDK 8 / x86_64)
Matrix: build-macos
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Build rockylinux (JDK 8 / x86_64)
Canceling since a higher priority waiting request for PR Build-6613 exists
Build rockylinux (JDK 8 / x86_64)
The operation was canceled.
PR Build
Canceling since a higher priority waiting request for PR Build-6613 exists
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 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/