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