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