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