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