Skip to content

proven: tests carries what a lane measured, beside the job that measured it - #72

Merged
aledbf merged 1 commit into
mainfrom
proven-measures
Oct 26, 2026
Merged

aledbf merged 1 commit into
mainfrom
proven-measures

Conversation

@aledbf

@aledbf aledbf commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

proven tests reads measure <name>=<value> lines off the answering runs' job logs (proven.Measures) and writes them as measures in the record, each with the job and its runner labels. spin's measuring e2e test logs them; hack/evidence carries them into evidence.json; the website's Measured page reads them with the release.

task lint, task test, task mutate green; the proven page says what measures is.

Plan: https://claude.ai/artifact/3cdj5BJsAkTtS9pWVhwksW (fase 4, PR 14).

🤖 Generated with Claude Code

…red it

A release's evidence said which tests passed and how long each took; a figure a reader can
compare - how long a boot, a snapshot, a resume takes - was nowhere, and a test's duration
measures the test. A measuring test logs `measure <name>=<value>`, the unit in the name, and
proven tests reads every such line off the jobs' logs into the record as measures, each with
the workflow, run, job and runner labels, so the website shows a number with the machine it was
measured on.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@aledbf
aledbf merged commit 90b43cc into main Oct 26, 2026
3 checks passed
@aledbf
aledbf deleted the proven-measures branch October 26, 2026 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant