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