Parent Log: http://ci.aztec-labs.com/0829684da0f6266d Command: b5d029682575c433 yarn-project/scripts/run_test.sh foundation/src/timer/timeout.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/fa4d5ef48c8de52059b5658bbd42e4514386f7db Env: REF_NAME=gh-readonly-queue/next/pr-15073-5ca43853c40a2b8bfbc2148d5fdd46c6f82a74eb CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 15:32:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15073_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_53b2ac7c4c28c35f_next 15:32:30 PASS src/timer/timeout.test.ts 15:32:30 timeout 15:32:30 ✓ execs within timeout (206 ms) 15:32:30 ✓ rejects with custom error on timeout (209 ms) 15:32:30 ✓ rejects if timeout is zero (2 ms) 15:32:30 ✓ rejects if timeout is negative (2 ms) 15:32:30 15:32:30 Test Suites: 1 passed, 1 total 15:32:30 Tests: 4 passed, 4 total 15:32:30 Snapshots: 0 total 15:32:30 Time: 0.839 s 15:32:30 Ran all test suites matching foundation/src/timer/timeout.test.ts. 15:32:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?