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