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