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