Parent Log: http://ci.aztec-labs.com/44fa37f6657e1f8c Command: 7cc721b132f3ad14 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/850aa9aff60a2bb682365766199619436d562288 Env: REF_NAME=gh-readonly-queue/next/pr-14990-355a15ab9ebeabff4c5709a97b85bb6c0f1c7b62 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 10:31:35 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14990_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next 10:31:36 PASS src/public/avm/serialization/bytecode_serialization.test.ts 10:31:36 Bytecode Serialization 10:31:36 ✓ Should deserialize using instruction set (3 ms) 10:31:36 ✓ Should serialize using instruction.serialize() (2 ms) 10:31:36 ✓ Should deserialize real instructions (2 ms) 10:31:36 ✓ Should serialize real instructions (2 ms) 10:31:36 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (15 ms) 10:31:36 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms) 10:31:36 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (8 ms) 10:31:36 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 10:31:36 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (10 ms) 10:31:36 10:31:36 Test Suites: 1 passed, 1 total 10:31:36 Tests: 9 passed, 9 total 10:31:36 Snapshots: 0 total 10:31:36 Time: 0.543 s 10:31:36 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 10:31:36 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?