Parent Log: http://ci.aztec-labs.com/5dcd1b40cb4c7fca Command: 7a41fc0e1576329f yarn-project/scripts/run_test.sh sequencer-client/src/sequencer/timetable.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/142e6cd5fbf7371f649078f9d6d08828585c664d Env: REF_NAME=gh-readonly-queue/next/pr-14610-016def8adbfe93f34b41a41f439b146b5318c895 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 12:57:51 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14610_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_820487f8760c5450_next 12:57:54 PASS src/sequencer/timetable.test.ts 12:57:54 sequencer-timetable 12:57:54 constructor 12:57:54 fails to construct an instance with too short slot duration (15 ms) 12:57:54 allows a slot duration of at least two ethereum slots (1 ms) 12:57:54 maxAllowedTime 12:57:54 computes time from slot start (1 ms) 12:57:54 computes time from slot end (1 ms) 12:57:54 returns an increasing time for each stage (1 ms) 12:57:54 assertTimeLeft 12:57:54 throws if time is up (2 ms) 12:57:54 does not throw if enough time left (1 ms) 12:57:54 handles negative seconds into slot 12:57:54 skips check if enforcement is off 12:57:54 getBlockProposalExecTimeEnd 12:57:54 sets deadline considering unused time from init phase 12:57:54 sets deadline considering starting before slot 12:57:54 sets deadline when building on time 12:57:54 sets deadline before current time if too late 12:57:54 getValidatorReexecTimeEnd 12:57:54 sets deadline 12:57:54 sets time available equal to block building 12:57:54 12:57:54 Test Suites: 1 passed, 1 total 12:57:54 Tests: 15 passed, 15 total 12:57:54 Snapshots: 0 total 12:57:54 Time: 1.598 s 12:57:54 Ran all test suites matching sequencer-client/src/sequencer/timetable.test.ts. 12:57:54 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?