Parent Log: http://ci.aztec-labs.com/eb6e7e1657c42119 Command: b895a7fa8f839b60 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/b80949775e5c27908a6055ad24592f7d98bdc45a Env: REF_NAME=gh-readonly-queue/next/pr-14816-fa159c5d52a45358479f951a547fed37f141a6ed CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Sat Jun 14 10:44:26 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14816_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:44:28 PASS src/public/avm/serialization/bytecode_serialization.test.ts 10:44:28 Bytecode Serialization 10:44:28 ✓ Should deserialize using instruction set (9 ms) 10:44:28 ✓ Should serialize using instruction.serialize() (2 ms) 10:44:28 ✓ Should deserialize real instructions (2 ms) 10:44:28 ✓ Should serialize real instructions (2 ms) 10:44:28 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (27 ms) 10:44:28 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (2 ms) 10:44:28 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (14 ms) 10:44:28 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 10:44:28 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (19 ms) 10:44:28 10:44:28 Test Suites: 1 passed, 1 total 10:44:28 Tests: 9 passed, 9 total 10:44:28 Snapshots: 0 total 10:44:28 Time: 0.789 s 10:44:28 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 10:44:28 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?