Skip to content

Print benchmark paths relative to the repo root - #21

Merged
lgoyal6 merged 1 commit into
mainfrom
fix/bench-log-relative-paths
Sep 7, 2026
Merged

lgoyal6 merged 1 commit into
mainfrom
fix/bench-log-relative-paths

Conversation

@lgoyal6

@lgoyal6 lgoyal6 commented Sep 7, 2026

Copy link
Copy Markdown
Owner

bench/data/run.log is tracked, and it recorded absolute paths from the machine that produced it, so a public repo carried the author's home directory layout on lines 2 and 454.

This changes run_matrix.sh to print paths relative to the repo root, and rewrites the two committed lines to match, so the log stays readable and the next run does not reintroduce it.

🤖 Generated with Claude Code

bench/data/run.log is committed as the provenance record for the CSVs beside
it, and BENCHMARKS.md points at those CSVs as the source of truth. Two of its
lines carried absolute paths, so a public repo advertised the operator's home
directory and username, and the transcript read as something that could only
have been produced on one particular laptop.

The log now names build/bench/bench and bench/data, which is what a reader
needs and all they need. run_matrix.sh, which writes those lines, strips the
repo root from any path under it before printing, so the next sweep does not
reintroduce what this commit removes. A BIN pointed somewhere outside the
tree still prints in full, because there the absolute path is the honest
answer.

Nothing reads run.log, so no consumer changes. The log is kept rather than
deleted because it is the only record of the sweep that produced the
committed CSVs.
@lgoyal6
lgoyal6 merged commit 31906d0 into main Sep 7, 2026
15 checks passed
@lgoyal6
lgoyal6 deleted the fix/bench-log-relative-paths branch September 7, 2026 00:32
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