feat: switch deposit currency with deposit pallet #898
Triggered via pull request
December 12, 2024 11:32
Status
Failure
Total duration
2h 2m 6s
Artifacts
–
check-code.yml
on: pull_request
Get HEAD commit message
4s
Matrix: Run Clippy checks
Check formatting
1m 15s
Check cargo-deny rules
1m 43s
Run Chopsticks tests
2h 1m
Matrix: Check Rustdoc
Matrix: Run Cargo tests
Matrix: Test runtime benchmarks
Matrix: Run try-runtime
Trigger GitLab CI
0s
Annotations
13 errors and 13 warnings
Run Clippy checks (--target wasm32-unknown-unknown --no-default-features --workspace --exclude ki...
Process completed with exit code 101.
|
Run Clippy checks (--all-targets --all-features)
Process completed with exit code 101.
|
Run Clippy checks (--all-targets)
Process completed with exit code 101.
|
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-db/dist/esm/base-sql.js#L85
ConnectionIsNotSetError: Connection with sqlite database is not established. Check connection configuration.
❯ SqliteQueryRunner.query src/driver/sqlite/SqliteQueryRunner.ts:71:19
❯ SelectQueryBuilder.loadRawResults src/query-builder/SelectQueryBuilder.ts:3805:43
❯ SelectQueryBuilder.executeEntitiesAndRawResults src/query-builder/SelectQueryBuilder.ts:3551:37
❯ SelectQueryBuilder.getRawAndEntities src/query-builder/SelectQueryBuilder.ts:1670:40
❯ SelectQueryBuilder.getOne src/query-builder/SelectQueryBuilder.ts:1697:36
❯ EntityManager.findOne src/entity-manager/EntityManager.ts:1215:14
❯ Repository.findOne src/repository/Repository.ts:597:29
❯ SqliteDatabase.queryStorage node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:85:69
❯ RemoteStorageLayer.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:32:25
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 "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 "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-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-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 "Send eKILT from other reserve location". 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-db/dist/esm/base-sql.js#L11
ConnectionIsNotSetError: Connection with sqlite database is not established. Check connection configuration.
❯ SqliteQueryRunner.query src/driver/sqlite/SqliteQueryRunner.ts:71:19
❯ SqliteQueryRunner.startTransaction src/driver/sqlite-abstract/AbstractSqliteQueryRunner.ts:112:24
❯ EntityManager.transaction src/entity-manager/EntityManager.ts:153:13
❯ SqliteDatabase.saveBlock node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:11:9
❯ Blockchain.saveBlockToDB node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:130:13
❯ Blockchain.onNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:246:9
❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:249:9
❯ 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.
|
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/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
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.
|
Check cargo-deny rules
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...
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 (--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)
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 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.
|