You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e513bf6
Browse filesBrowse the repository at this point in the historyBrowse files
The inter-version benchmark reaches two releases further back (#1178)
Two of the five rows in key-commits.txt read "did not build". The reason was
not the case being measured: CommonFunctionsInterVersion uses nothing but the
public API and compiles against every one of them. It was the other cases in
the same project. MatchingEngine reaches `MatchedRules` and `Patterns`, which
were internal until v2.3.0, and TransformationLayer names
`Transformation.Rationalization`, which did not exist at v2.1.0 -- so the
project failed to compile and took the row with it, and the file that would
have run was never the problem.
`-p:InterVersionOnly=true` compiles the case that runs and leaves the rest out.
Measured rather than argued: v2.1.0 and v2.2.0 now build and run, and v2.1.0
produced a full set of figures -- fifteen cases with means and allocations,
written to measured-CommonFunctionsInterVersion.json the way every other row
is. The unflagged build is unchanged and still compiles every case.
The note this replaces said reaching further back would mean conditioning the
benchmark project on which commit it is pointed at, and that this would break
the comparison because the reason the columns compare is that the benchmark
does not vary. The first half was right and the second does not follow. The
flag is per-purpose, not per-commit: the script passes it for every row
including master, so each column compiles the same files and runs the same
file. Conditioning per commit would have broken the comparison; conditioning
per purpose does not touch it.
Closes#529 -- the measurement half landed in #1140, and this was the
limitation recorded against it. The two steps deliberately left out there are
unchanged and remain decisions rather than work: the schedule is weekly plus
workflow_dispatch rather than daily, and nothing is pushed to a website
because neither AngouriMathLab/performance-reports nor its tools repository
exists.
Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments