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