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