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