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

I0817

Phase timing and work counters behind MJ_TIMING

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
M004
Milestone status
ACTIVE
Wave
0
Waiting on
none
Holds back
I0818I0819I0821I0823I0832I0833I0837
Behind it in all
25
Evidence
1 of 1

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 I0817

majordomus plan verify I0817

majordomus plan done I0817

What it is

Objective
Time every validator and count every YAML flatten and git call when MJ_TIMING is set, and report them ranked at exit.
Why
Nothing else in this milestone can be measured without it; optimisation without a ranking is guessing.
Now
Landed on feature/performance-truth as 77f5d79: the dispatcher declares one phase per validator, mj_git and mj_yaml_flatten count.
Wanted
Phases and counters are the vocabulary every later issue reports in.
Done when
unknown: the record declares no `completion`
Risk
The clock is EPOCHREALTIME where bash has it and perl otherwise; whole seconds where neither exists, and the report says which.

Acceptance

  • The report ranks phases by time and sums counters on stderr, with the command output untouched
  • Off, a phase or a count costs one test and no subprocess
Validation
MJ_TIMING=1 bin/majordomus doctorbash test/run.sh 08_no_forbidden_constructs
Evidence required
phase_timing
Evidence present
phase_timing

Scope

Touches
lib/common.shlib/doctrine.shtest/cases/08_no_forbidden_constructs.sh
Not
A tracing backendTiming that is on when MJ_TIMING is unset
Depends on
none
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
2026-09-05T01:35:00Z
Verified
2026-09-05T01:44:00Z
Completed
2026-09-05T01:44:00Z

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.