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