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