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