Parent Log: http://ci.aztec-labs.com/d700f1f37339a11a Command: be792e9a8a7f847e yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/a8c553f203c98e5ca274e763c8e51daaaaf760d6 Env: REF_NAME=gh-readonly-queue/next/pr-15017-30660269b33bab8cca354c41659533acf4d48e07 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 09:37:54 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15017_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:37:56 PASS src/public/avm/serialization/bytecode_serialization.test.ts 09:37:56 Bytecode Serialization 09:37:56 ✓ Should deserialize using instruction set (5 ms) 09:37:56 ✓ Should serialize using instruction.serialize() (1 ms) 09:37:56 ✓ Should deserialize real instructions (2 ms) 09:37:56 ✓ Should serialize real instructions (1 ms) 09:37:56 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (21 ms) 09:37:56 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (3 ms) 09:37:56 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (10 ms) 09:37:56 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 09:37:56 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (11 ms) 09:37:56 09:37:56 Test Suites: 1 passed, 1 total 09:37:56 Tests: 9 passed, 9 total 09:37:56 Snapshots: 0 total 09:37:56 Time: 0.806 s 09:37:56 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 09:37:56 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?