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