Process completed with exit code 101.

System.IO.IOException: No space left on device : '/home/runner/runners/2.319.1/_diag/Worker_20240920-112159-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/runners/2.319.1/_diag/Worker_20240920-112159-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Common.Tracing.Error(Exception exception) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.319.1/_diag/Worker_20240920-112159-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at System.Diagnostics.TraceSource.Flush() at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing) at GitHub.Runner.Common.TraceManager.Dispose() at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing) at GitHub.Runner.Common.HostContext.Dispose() at GitHub.Runner.Worker.Program.Main(String[] args)

The hosted runner: GitHub Actions 13 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The hosted runner: GitHub Actions 31 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

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.

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.

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.

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 ❯ Block.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block.js:118:21 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.

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/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.

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.

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.

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/xcm/assetHub/peregrine/initiateWithdrawAssetsFromPeregrineAssetHub.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 "Initiate withdraw assets Peregrine Account Alice -> AH Account Alice". 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.

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/xcm/assetHub/peregrine/initiateWithdrawAssetsFromPeregrineAssetHub.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 "Initiate withdraw assets Peregrine Account Alice -> AH Account Alice". 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.

Error: Snapshot `Limited Reserve V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob > sender AssetHub::polkadotXcm::[FeesPaid,Attempted,Sent] 1` mismatched - Expected + Received @@ -3,11 +3,11 @@ "data": { "outcome": { "Complete": { "used": { "proofSize": "(rounded 6200)", - "refTime": "(rounded 290000000)", + "refTime": "(rounded 300000000)", }, }, }, }, "method": "Attempted", @@ -16,11 +16,11 @@ { "data": { "fees": [ { "fun": { - "Fungible": "(rounded 310000000)", + "Fungible": "(rounded 300000000)", }, "id": { "interior": "Here", "parents": 1, }, ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 This error originated in "src/tests/xcm/assetHub/peregrine/limitedReserveTransferAssetHubPeregrine.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 "Limited Reserve V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob". 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.

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...

The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...

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...

The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...

The command [sudo apt-get clean] failed to complete successfully. Proceeding...