Parent Log: http://ci.aztec-labs.com/56b1dc937ab080fe Command: fb52012d377692f9 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1e338a3fb2e2077f1feaee8b86c42644ff8a5352 Env: REF_NAME=gh-readonly-queue/next/pr-15075-fa4d5ef48c8de52059b5658bbd42e4514386f7db CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:42:15 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15075_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:42:16 PASS src/public/avm/serialization/bytecode_serialization.test.ts 16:42:16 Bytecode Serialization 16:42:16 ✓ Should deserialize using instruction set (4 ms) 16:42:16 ✓ Should serialize using instruction.serialize() (1 ms) 16:42:16 ✓ Should deserialize real instructions (2 ms) 16:42:16 ✓ Should serialize real instructions (1 ms) 16:42:16 ✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (17 ms) 16:42:16 ✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms) 16:42:16 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction (7 ms) 16:42:16 ✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms) 16:42:16 ✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (26 ms) 16:42:16 16:42:16 Test Suites: 1 passed, 1 total 16:42:16 Tests: 9 passed, 9 total 16:42:16 Snapshots: 0 total 16:42:16 Time: 0.739 s 16:42:16 Ran all test suites matching simulator/src/public/avm/serialization/bytecode_serialization.test.ts. 16:42:16 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?