fix: add required migration (#856) #1015
check-code.yml
on: push
Get HEAD commit message
4s
Matrix: Run Clippy checks
Check formatting
1m 37s
Check cargo-deny rules
1m 45s
Run Chopsticks tests
1h 37m
Matrix: Check Rustdoc
Matrix: Run Cargo tests
Matrix: Test runtime benchmarks
Matrix: Run try-runtime
Trigger GitLab CI
3s
Annotations
10 errors and 33 warnings
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents
❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19
❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44
❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47
❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13
This error originated in "src/tests/switchPallet/pauseSwitch.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch ePILTs against PILTs while paused". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents
❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19
❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44
❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47
❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13
This error originated in "src/tests/switchPallet/pauseSwitch.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Withdraw ROCs while switch is paused". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents
❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19
❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44
❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47
❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::xcmpQueue::[XcmpMessageSent] 2` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::assetSwitchPool1::[LocalToRemoteSwitchExecuted] 2` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::balances::[Transfer] 2` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::xcmpQueue::[XcmpMessageSent] 3` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::assetSwitchPool1::[LocalToRemoteSwitchExecuted] 3` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::balances::[Transfer] 3` mismatched
❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51
This error originated in "src/tests/switchPallet/switchConfig.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Switch KILTs against EKILTs no enough DOTs on AH". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/api.js#L65
Error: WebSocket is not connected
❯ node_modules/@polkadot/rpc-provider/ws/index.js:273:27
❯ WsProvider.__internal__send node_modules/@polkadot/rpc-provider/ws/index.js:270:16
❯ WsProvider.send node_modules/@polkadot/rpc-provider/ws/index.js:258:34
❯ Api.send node_modules/@acala-network/chopsticks-core/dist/esm/api.js:65:31
❯ Api.getSystemChain node_modules/@acala-network/chopsticks-core/dist/esm/api.js:74:21
❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:354:32
❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47
❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13
This error originated in "src/tests/switchPallet/trappedAssets.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Trapped assets". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Get HEAD commit message
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check formatting
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Check formatting
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--target wasm32-unknown-unknown --no-default-features --workspace --exclude ki...
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run Clippy checks (--target wasm32-unknown-unknown --no-default-features --workspace --exclude ki...
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--target wasm32-unknown-unknown --no-default-features --workspace --exclude ki...
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--all-targets)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run Clippy checks (--all-targets)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--all-targets)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--all-targets --all-features)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run Clippy checks (--all-targets --all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Clippy checks (--all-targets --all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Check Rustdoc
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check Rustdoc
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Check Rustdoc
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Check Rustdoc (--all-features)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check Rustdoc (--all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Check Rustdoc (--all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run try-runtime (peregrine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run try-runtime (peregrine)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run try-runtime (peregrine)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run try-runtime (spiritnet)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run try-runtime (spiritnet)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run try-runtime (spiritnet)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Cargo tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run Cargo tests
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Cargo tests
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Cargo tests (--all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Cargo tests (--all-features)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Run Chopsticks tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run Chopsticks tests
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release.
A separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
Test runtime benchmarks (spiritnet)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Test runtime benchmarks (peregrine)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|