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