Parent Log: http://ci.aztec-labs.com/6cc9fa695c7cfc03 Command: 4ef547fa5e299294 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d4893155ff105399557b55c16450c39921c70d11 Env: REF_NAME=gh-readonly-queue/next/pr-15218-7edf16da6c056f9499e2dfd9c71fb9b7580f9bfc CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 10:28:23 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15218_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next 10:28:25 PASS src/public/avm/serialization/bytecode_serialization.test.ts 10:28:25 Bytecode Serialization 10:28:25 ✓ Should deserialize using instruction set (4 ms) 10:28:25 ✓ Should serialize using instruction.serialize() (1 ms) 10:28:25 ✓ Should deserialize real instructions (1 ms) 10:28:25 ✓ Should serialize real instructions (1 ms) 10:28:25 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (23 ms) 10:28:25 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms) 10:28:25 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (9 ms) 10:28:25 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 10:28:25 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (17 ms) 10:28:25 10:28:25 Test Suites: 1 passed, 1 total 10:28:25 Tests: 9 passed, 9 total 10:28:25 Snapshots: 0 total 10:28:25 Time: 0.665 s 10:28:25 Ran all test suites matching simulator/src/public/avm/serialization/bytecode_serialization.test.ts. 10:28:25 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?