Show reverse-transformed events in the debugging trace #20973
ci.yml
on: pull_request
Build Nextest Archive (Forge)
1m 31s
Build Nextest Archive (Forge Native)
2m 2s
Build Nextest Archive (Cast)
2m 19s
Get Scarb versions
Workspace Tests
3m 23s
Test special conditions
1m 8s
Test Forge Scarb Plugin
3m 32s
Test Cast / Doctests
1m 36s
Test Ledger
3m 27s
Lint and Format
2m 37s
Test Building Docs
3m 36s
Matrix: Test Forge / E2E Tests
Matrix: Test Forge / Integration Tests
Matrix: Test Forge / E2E Tests (native)
Matrix: Test Forge / Integration Tests (native)
Matrix: Test Cast
Matrix: test-forge-e2e-snap
Annotations
60 errors and 21 warnings
|
Test special conditions
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Cast / Doctests
There was an error when restoring cache: failed to find Scarb.lock
|
|
Build Nextest Archive (Cast)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Lint and Format
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / E2E Tests (native) (1)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (native) (1)
The operation was canceled.
|
|
Test Forge / Integration Tests (native) (2)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (native) (2)
The operation was canceled.
|
|
Test Forge / Integration Tests (native) (2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / Integration Tests (native) (3)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (native) (3)
The operation was canceled.
|
|
Test Forge / Integration Tests (native) (3)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / E2E Tests (native) (2)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (native) (2)
The operation was canceled.
|
|
Test Forge / E2E Tests (native) (2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / Integration Tests (1)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (1)
The operation was canceled.
|
|
Test Forge / Integration Tests (2)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (2)
The operation was canceled.
|
|
Test Forge / E2E Tests (native) (3)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (native) (3)
The operation was canceled.
|
|
Test Forge / E2E Tests (native) (3)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / Integration Tests (native) (1)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (native) (1)
The operation was canceled.
|
|
Test Forge / Integration Tests (native) (1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Ledger
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Ledger
The operation was canceled.
|
|
Test Cast (3)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Cast (3)
The operation was canceled.
|
|
Test Cast (3)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Workspace Tests
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Workspace Tests
The operation was canceled.
|
|
Workspace Tests
unable to access 'https://github.com/foundry-rs/starknet-foundry/': The requested URL returned error: 500
|
|
Test Cast (2)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Cast (2)
The operation was canceled.
|
|
Test Cast (2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Cast (1)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Cast (1)
The operation was canceled.
|
|
Test Cast (1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / E2E Tests (3)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (3)
The operation was canceled.
|
|
Test Forge / E2E Tests (3)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / E2E Tests (2)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (2)
The operation was canceled.
|
|
Test Forge / E2E Tests (2)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge / E2E Tests (1)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / E2E Tests (1)
The operation was canceled.
|
|
Test Forge / E2E Tests (1)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge Scarb Plugin
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge Scarb Plugin
The operation was canceled.
|
|
Test Forge Scarb Plugin
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Forge Scarb Plugin
unable to access 'https://github.com/foundry-rs/starknet-foundry/': The requested URL returned error: 500
|
|
Test Forge / Integration Tests (3)
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Forge / Integration Tests (3)
The operation was canceled.
|
|
Test Forge / Integration Tests (3)
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Building Docs
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test Building Docs
The operation was canceled.
|
|
Test Building Docs
There was an error when restoring cache: failed to find Scarb.lock
|
|
Test Building Docs
unable to access 'https://github.com/foundry-rs/starknet-foundry/': The requested URL returned error: 500
|
|
CI
Canceling since a higher priority waiting request for event-debugging/reverse-transformed-events-in-trace exists
|
|
Test special conditions
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, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Build Nextest Archive (Forge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Test Cast / Doctests
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, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Build Nextest Archive (Forge Native)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Build Nextest Archive (Cast)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, software-mansion/setup-universal-sierra-compiler@v1, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Lint and Format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Test Forge / Integration Tests (native) (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / Integration Tests (native) (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / E2E Tests (native) (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / E2E Tests (native) (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / Integration Tests (native) (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Cast (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Cast (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Cast (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / E2E Tests (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / E2E Tests (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge / E2E Tests (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Forge Scarb Plugin
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 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/
|
|
Test Forge / Integration Tests (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, software-mansion/setup-universal-sierra-compiler@v1. 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/
|
|
Test Building Docs
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, Swatinem/rust-cache@9d47c6ad4b02e050fd481d890b2ea34778fd09d6. 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/
|
|
Test Building Docs
cargo-binstall fallback does not support prebuilt binaries for mdbook-variables@0.3.0 on this platform (x86_64); use 'cargo-install' fallback instead
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
nextest-archive-cast-Linux
|
317 MB |
sha256:5f8652c02c01381847b0fd841aa7f2d3260b86fcca2f7e1ab9a794ce5939b9fb
|
|
|
nextest-archive-forge-Linux
|
278 MB |
sha256:79ad729f2164cf6c410c3492f17e588c6c728a2b934953c63cdc9d3ba6ffdba0
|
|
|
nextest-archive-forge-native-Linux
|
416 MB |
sha256:a0db13096d81762370d8e662f97b986cf274ce7265f557c6c0226ad10838178f
|
|