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