Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0834

The test runner reports per-case time and the suite budget

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
M004
Milestone status
ACTIVE
Wave
4
Waiting on
I0828
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI0828I0828 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0834

majordomus plan verify I0834

majordomus plan done I0834

What it is

Objective
Print each case's wall time in test/run.sh, sort the slowest at the end, and record the suite's total in the benchmark history as a system target.
Why
A single case costs 29 s because it runs doctor several times; the suite's half hour is the same cost multiplied.
Now
run.sh prints ok or FAIL and nothing about time.
Wanted
Per-case times printed, the suite under ten minutes on this repository after the doctor fixes, the total recorded.
Done when
unknown: the record declares no `completion`
Risk
Times in the runner output must not be asserted by any case.

Acceptance

  • run.sh prints a time per case and a ranked tail
  • The suite total appears in bench --list as a system target
Validation
bash test/run.sh 01_init
Evidence required
doctor_under_budget
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
test/run.shlib/bench.sh
Not
Parallel test execution
Depends on
I0828
Priority
p0
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-05
Updated
2026-09-05
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.