Skip to content

feat: add new DID runtime APIs to aid with DID deletion #1016

feat: add new DID runtime APIs to aid with DID deletion

feat: add new DID runtime APIs to aid with DID deletion #1016

Triggered via pull request January 29, 2025 08:32
Status Failure
Total duration 1h 36m 44s
Artifacts

check-code.yml

on: pull_request
Get HEAD commit message
4s
Get HEAD commit message
Matrix: Run Clippy checks
Check formatting
1m 28s
Check formatting
Check cargo-deny rules
1m 36s
Check cargo-deny rules
Run Chopsticks tests
1h 36m
Run Chopsticks tests
Matrix: Check Rustdoc
Matrix: Run Cargo tests
Matrix: Test runtime benchmarks
Matrix: Run try-runtime
Trigger GitLab CI
0s
Trigger GitLab CI
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 21 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 "Send ROCs while switch 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 "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/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.
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...
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 --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.
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.
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)
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)
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)
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
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
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.