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