Parent Log: http://ci.aztec-labs.com/cc289456ecfb3257 Command: 582720422b3f4dff yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/79e9bd1698f4bba6deade8f76c676f9bbb12ff74 Env: REF_NAME=gh-readonly-queue/staging/pr-15192-505a3c071181dbc5242dc8b655a9b2d69988c8db CURRENT_VERSION=1.0.0 CI_FULL=1 Date: Mon Jun 23 13:25:50 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15192_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_staging 13:25:51 PASS src/public/avm/serialization/bytecode_serialization.test.ts 13:25:51 Bytecode Serialization 13:25:51 ✓ Should deserialize using instruction set (3 ms) 13:25:51 ✓ Should serialize using instruction.serialize() (1 ms) 13:25:51 ✓ Should deserialize real instructions (1 ms) 13:25:51 ✓ Should serialize real instructions (1 ms) 13:25:51 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (14 ms) 13:25:51 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms) 13:25:51 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (6 ms) 13:25:51 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 13:25:51 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (22 ms) 13:25:51 13:25:51 Test Suites: 1 passed, 1 total 13:25:51 Tests: 9 passed, 9 total 13:25:51 Snapshots: 0 total 13:25:51 Time: 0.668 s 13:25:51 Ran all test suites matching simulator/src/public/avm/serialization/bytecode_serialization.test.ts. 13:25:51 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?