Parent Log: http://ci.aztec-labs.com/345c5ed524d6c3dd Command: 557c108a8ed544a3 yarn-project/scripts/run_test.sh foundation/src/timer/timeout.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/ed4f6d71e2ea98f43186114eb914d54b87dd1183 Env: REF_NAME=gh-readonly-queue/next/pr-15116-433ba6218aed45169029991a493e4232b30b8ec6 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 19:34:09 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15116_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_53b2ac7c4c28c35f_next 19:34:11 PASS src/timer/timeout.test.ts 19:34:11 timeout 19:34:11 ✓ execs within timeout (205 ms) 19:34:11 ✓ rejects with custom error on timeout (210 ms) 19:34:11 ✓ rejects if timeout is zero (3 ms) 19:34:11 ✓ rejects if timeout is negative (3 ms) 19:34:11 19:34:11 Test Suites: 1 passed, 1 total 19:34:11 Tests: 4 passed, 4 total 19:34:11 Snapshots: 0 total 19:34:11 Time: 0.887 s 19:34:11 Ran all test suites matching foundation/src/timer/timeout.test.ts. 19:34:11 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?