Tasks bench: keep seeded dates in the active view #1243

Open
opened 2026-10-06 22:57:23 +00:00 by kayg · 2 comments
Owner

The Tasks UI profile seeds every Task with fixed When 2026-10-02 / Deadline 2026-10-04 values. The real app opens its default Next 7 days view, so after those dates pass the fixture contains zero visible rows and the benchmark fails waiting for List content. Reproduction and evidence are recorded in target/tmp/tasks-list-1k-timeout-2026-10-07.txt.

Expected: profile fixtures stay in the active default view on every run.
Actual: on 2026-10-07, the 390 px Board shell appeared but its filtered List had no row; the profile waited 180 seconds and timed out.
Severity: minor test/tooling defect. Fix: generate When/Deadline dates relative to run date, then rerun the profile.

The Tasks UI profile seeds every Task with fixed `When 2026-10-02` / `Deadline 2026-10-04` values. The real app opens its default Next 7 days view, so after those dates pass the fixture contains zero visible rows and the benchmark fails waiting for List content. Reproduction and evidence are recorded in `target/tmp/tasks-list-1k-timeout-2026-10-07.txt`. Expected: profile fixtures stay in the active default view on every run. Actual: on 2026-10-07, the 390 px Board shell appeared but its filtered List had no row; the profile waited 180 seconds and timed out. Severity: minor test/tooling defect. Fix: generate When/Deadline dates relative to run date, then rerun the profile.
Author
Owner

Fixed on job/bash-tasks in 5c02bb26c (fix(bench): keep Tasks profile dates active (#1243)). The profile now computes its When and Deadline dates relative to the run date so the default Next 7 days view has real rows. node --check apps/web/e2e/tasks-perf.mjs passed; the production 1,000-Task profile rerun is in progress.

Fixed on `job/bash-tasks` in `5c02bb26c` (`fix(bench): keep Tasks profile dates active (#1243)`). The profile now computes its When and Deadline dates relative to the run date so the default Next 7 days view has real rows. `node --check apps/web/e2e/tasks-perf.mjs` passed; the production 1,000-Task profile rerun is in progress.
Author
Owner

The run-relative date fix in 5c02bb26c was correct but did not by itself populate the benchmark: the route also needed to select view=next-7-days. That separate profile bug is #1246, fixed in bc66e4a5b. Corrected 1,000-Task route readiness completed at both phone and desktop widths. The later 4x CPU Board drag probe stopped before writing the profile JSON and is tracked in #1258.

The run-relative date fix in `5c02bb26c` was correct but did not by itself populate the benchmark: the route also needed to select `view=next-7-days`. That separate profile bug is #1246, fixed in `bc66e4a5b`. Corrected 1,000-Task route readiness completed at both phone and desktop widths. The later 4x CPU Board drag probe stopped before writing the profile JSON and is tracked in #1258.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1243
No description provided.