Parent Log: http://ci.aztec-labs.com/d9cbe39da05505e1 Command: f682b45a820409ef yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/c0e766a133071c44b2c0d8fac5df352c6e059df1 Env: REF_NAME=gh-readonly-queue/next/pr-15015-cf8be0f9e81e248048560619de041e90d9d6990a CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 07:56:16 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15015_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next 07:56:18 PASS src/public/avm/serialization/bytecode_serialization.test.ts 07:56:18 Bytecode Serialization 07:56:18 ✓ Should deserialize using instruction set (6 ms) 07:56:18 ✓ Should serialize using instruction.serialize() (2 ms) 07:56:18 ✓ Should deserialize real instructions (2 ms) 07:56:18 ✓ Should serialize real instructions (2 ms) 07:56:18 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (18 ms) 07:56:18 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (2 ms) 07:56:18 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (13 ms) 07:56:18 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 07:56:18 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (28 ms) 07:56:18 07:56:18 Test Suites: 1 passed, 1 total 07:56:18 Tests: 9 passed, 9 total 07:56:18 Snapshots: 0 total 07:56:18 Time: 0.84 s 07:56:18 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 07:56:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?