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