Parent Log: http://ci.aztec-labs.com/3e3413f71a24d5fb Command: 5043c2a28c0b54c6 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/355a15ab9ebeabff4c5709a97b85bb6c0f1c7b62 Env: REF_NAME=gh-readonly-queue/next/pr-14961-98fbe17330964452777de26d56f0a3ed5633aca1 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 10:31:08 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14961_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:09 PASS src/public/avm/serialization/bytecode_serialization.test.ts 10:31:09 Bytecode Serialization 10:31:09 ✓ Should deserialize using instruction set (3 ms) 10:31:09 ✓ Should serialize using instruction.serialize() (1 ms) 10:31:09 ✓ Should deserialize real instructions (2 ms) 10:31:09 ✓ Should serialize real instructions (1 ms) 10:31:09 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (17 ms) 10:31:09 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (2 ms) 10:31:09 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (7 ms) 10:31:09 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 10:31:09 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (9 ms) 10:31:09 10:31:09 Test Suites: 1 passed, 1 total 10:31:09 Tests: 9 passed, 9 total 10:31:09 Snapshots: 0 total 10:31:09 Time: 0.548 s 10:31:09 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 10:31:09 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?