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