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