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