chore: update status badge #104
Triggered via pull request
September 2, 2024 12:59
Status
Failure
Total duration
1h 23m 48s
Artifacts
–
check-code.yml
on: pull_request
Matrix: Run Clippy checks
Matrix: Check Rustdoc
Matrix: Run Cargo tests
Matrix: Run try-runtime
Annotations
12 errors and 18 warnings
Run try-runtime (peregrine)
Process completed with exit code 101.
|
Run try-runtime (spiritnet)
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/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-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.
|
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.getKeysPaged node_modules/@acala-network/chopsticks-core/dist/esm/api.js:131:25
❯ RemoteStorageLayer.getKeysPaged node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:61:30
❯ parentFetchKeys node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:202:56
❯ StorageLayer.getKeysPaged node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:272:26
❯ parentFetchKeys node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:202:56
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/fullFlowSwitch.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 "Full e2e tests". 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/fullFlowSwitch.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 "Full e2e tests". 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/fullFlowSwitch.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 "Full e2e tests". 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/relayToken.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 "User gets dusted with ROCs". 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/switchEkiltAgainstKilt.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 on Peregrine". 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/switchEkiltAgainstKilt.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 on Peregrine". 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
❯ processTicksAndRejections node:internal/process/task_queues:95:5
❯ 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/switchEkiltAgainstKilt.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 on Peregrine". 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.
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
|
Run try-runtime (peregrine)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
|
Run try-runtime (spiritnet)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
|