Rely on casm debug info instead of libfunc names to exclude statements from coverage #818
ci.yml
on: pull_request
Check rust formatting
20s
Check cairo formatting
9s
Check linter
17s
Check typos
7s
Matrix: Tests
Annotations
12 errors and 10 warnings
|
Check cairo formatting
There was an error when restoring cache: failed to find Scarb.lock
|
|
Check linter
Process completed with exit code 101.
|
|
Tests (2.18.0)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.13.1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.16.1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.17.0)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.12.2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.14.0)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.15.2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.9.4)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.10.1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.11.4)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Tests (2.18.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.13.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.16.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.17.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.12.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.14.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.15.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.9.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.10.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Tests (2.11.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: software-mansion/setup-universal-sierra-compiler@v1. 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/
|