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