Parent Log: http://ci.aztec-labs.com/7b3e6e8a2abdd89b Command: 9e91553d04f5b22d yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/10badd24359b04680068afd9ca24407383374db1 Env: REF_NAME=gh-readonly-queue/next/pr-15019-7d223783d91db15002a09abc1b52d1455eb3e3da CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 16 11:10:52 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15019_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next 11:10:53 PASS src/public/avm/serialization/bytecode_serialization.test.ts 11:10:53 Bytecode Serialization 11:10:53 ✓ Should deserialize using instruction set (3 ms) 11:10:53 ✓ Should serialize using instruction.serialize() (2 ms) 11:10:53 ✓ Should deserialize real instructions (1 ms) 11:10:53 ✓ Should serialize real instructions (1 ms) 11:10:53 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (15 ms) 11:10:53 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms) 11:10:53 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (8 ms) 11:10:53 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 11:10:53 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (10 ms) 11:10:53 11:10:53 Test Suites: 1 passed, 1 total 11:10:53 Tests: 9 passed, 9 total 11:10:53 Snapshots: 0 total 11:10:53 Time: 0.542 s 11:10:53 Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i. 11:10:53 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?