Parent Log: http://ci.aztec-labs.com/a0a5ca8d8b3bb5c7 Command: f643ae060f517c84 yarn-project/scripts/run_test.sh sequencer-client/src/sequencer/timetable.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be78cf2e908c8f2f34676d72c74c8b92a3f591d1 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Fri Jun 20 23:00:11 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 23:00:13 PASS src/sequencer/timetable.test.ts 23:00:13 sequencer-timetable 23:00:13 constructor 23:00:13 ✓ fails to construct an instance with too short slot duration (15 ms) 23:00:13 ✓ allows a slot duration of at least two ethereum slots (2 ms) 23:00:13 maxAllowedTime 23:00:13 ✓ computes time from slot start (1 ms) 23:00:13 ✓ computes time from slot end (1 ms) 23:00:13 ✓ returns an increasing time for each stage (1 ms) 23:00:13 assertTimeLeft 23:00:13 ✓ throws if time is up (1 ms) 23:00:13 ✓ does not throw if enough time left (1 ms) 23:00:13 ✓ handles negative seconds into slot 23:00:13 ✓ skips check if enforcement is off 23:00:13 getBlockProposalExecTimeEnd 23:00:13 ✓ sets deadline considering unused time from init phase (1 ms) 23:00:13 ✓ sets deadline considering starting before slot 23:00:13 ✓ sets deadline when building on time (1 ms) 23:00:13 ✓ sets deadline before current time if too late 23:00:13 getValidatorReexecTimeEnd 23:00:13 ✓ sets deadline 23:00:13 ✓ sets time available equal to block building 23:00:13 23:00:13 Test Suites: 1 passed, 1 total 23:00:13 Tests: 15 passed, 15 total 23:00:13 Snapshots: 0 total 23:00:13 Time: 1.421 s 23:00:13 Ran all test suites matching sequencer-client/src/sequencer/timetable.test.ts. 23:00:13 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?