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