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