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