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