Parent Log: http://ci.aztec-labs.com/4f0a05f8d1d5ca3f Command: 97e7ef9a556fd7e6 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/015cb0cadef6a41094c3649f32a735392e1b9693 Env: REF_NAME=gh-readonly-queue/master/pr-15027-e9a2301883801edbe36ea8bba05dcca7e714f30a CURRENT_VERSION=0.87.8 CI_FULL=1 Date: Wed Jun 18 14:25:40 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15027_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_master 14:25:41 PASS src/public/avm/serialization/bytecode_serialization.test.ts 14:25:41 Bytecode Serialization 14:25:41 ✓ Should deserialize using instruction set (4 ms) 14:25:41 ✓ Should serialize using instruction.serialize() (1 ms) 14:25:41 ✓ Should deserialize real instructions (2 ms) 14:25:41 ✓ Should serialize real instructions (1 ms) 14:25:41 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (44 ms) 14:25:41 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (3 ms) 14:25:41 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (29 ms) 14:25:41 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 14:25:41 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (16 ms) 14:25:41 14:25:41 Test Suites: 1 passed, 1 total 14:25:41 Tests: 9 passed, 9 total 14:25:41 Snapshots: 0 total 14:25:41 Time: 0.66 s 14:25:41 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 14:25:41 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?