Parent Log: http://ci.aztec-labs.com/704f35e55ac1c274 Command: b54d5ade67e7ffc9 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/instruction_serialization.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/347f29fb98cc855ead57129b4d1a444d9fb16820 Env: REF_NAME=gh-readonly-queue/next/pr-15059-16fc84676c7308fa5f7ca4a54b67319803d0f5b7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:01:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15059_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_42c42ac226abcac4_next 16:01:30 PASS src/public/avm/serialization/instruction_serialization.test.ts 16:01:30 Instruction Serialization 16:01:30 ✓ Should serialize all types from OperandType[] (5 ms) 16:01:30 ✓ Should deserialize all types from OperandType[] (1 ms) 16:01:30 16:01:30 Test Suites: 1 passed, 1 total 16:01:30 Tests: 2 passed, 2 total 16:01:30 Snapshots: 0 total 16:01:30 Time: 0.691 s 16:01:30 Ran all test suites matching simulator/src/public/avm/serialization/instruction_serialization.test.ts. 16:01:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?