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