kami/test-e2e
1
0
Fork 0
Code Issues 20 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

Report the slowest check in the summary footer #36

New Issue
Open
opened 2026-08-30 12:29:34 +02:00 by claude · 0 comments
claude commented 2026-08-30 12:29:34 +02:00
Contributor
Copy Link
Copy Source

--summary prints one line per check. After those lines, print a footer naming the slowest check and its elapsed milliseconds, in the form slowest: <name> (<n>ms).

Plan this as THREE phases:

  1. Record each check's elapsed milliseconds beside its existing result, with no output change.
  2. The footer printed by --summary from those recorded values.
  3. The usage text in --help, and assertions in scripts/test_healthcheck.sh.

Work one phase at a time

Implement phase N, request its verification, and only then begin phase N+1.

Verification policy for this project

Only two commands may appear on a run: line, exactly:

  • ["bash", "-n", ""]
  • ["bash", "scripts/orchestra_e2e_healthcheck.sh"]

Anything else is refused when you seal the plan. Give every phase at least one automated check from that list and at least one manual check.

Research first

Establish at least three findings with distinct confidence: at least one fact, one inference, one assumption.

Acceptance:

  • --summary ends with the slowest line.
  • --quiet suppresses it, and every other flag is unchanged.
`--summary` prints one line per check. After those lines, print a footer naming the slowest check and its elapsed milliseconds, in the form `slowest: <name> (<n>ms)`. Plan this as THREE phases: 1. Record each check's elapsed milliseconds beside its existing result, with no output change. 2. The footer printed by --summary from those recorded values. 3. The usage text in `--help`, and assertions in scripts/test_healthcheck.sh. ## Work one phase at a time Implement phase N, request its verification, and only then begin phase N+1. ## Verification policy for this project Only two commands may appear on a run: line, exactly: - ["bash", "-n", "<path>"] - ["bash", "scripts/orchestra_e2e_healthcheck.sh"] Anything else is refused when you seal the plan. Give every phase at least one automated check from that list and at least one manual check. ## Research first Establish at least three findings with distinct confidence: at least one fact, one inference, one assumption. Acceptance: - --summary ends with the slowest line. - --quiet suppresses it, and every other flag is unchanged.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kami
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kami/test-e2e#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?