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