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