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