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