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 eb8e2ee
Browse filesBrowse the repository at this point in the historyBrowse files
ci: generate baseline benchmark projects with the baseline release generator (#921)
* ci: generate release benchmark projects with each version's own generator
The release performance comparison generated its benchmark projects with
the candidate's generator and compiled them with the previous release, so
any generator syntax newer than that release (such as FUNCTION
descriptions) failed the baseline before timing. The baseline now runs
projects written by its own generator: the release tag's source is
extracted with git archive (or taken from --baseline-source) and its
write_pristine_projects runs with this interpreter, with cwd and
PYTHONPATH set to that source, through the checkout generator runner
shared with the same-runner compile ratio job. The candidate keeps its
own generator. Generation failures stop the comparison with the
generator's stderr tail, and the report and evidence record the
baseline's generator.
* test: make the release-performance self-comparison E2E independent of runner noise
The E2E compares one build with itself using a single run, so asserting a
passed verdict depended on wall-time noise (a 1.31x wall ratio at 0.99x
CPU failed CI). It now asserts the report structure, every command row,
the per-side generator markers and the recorded evidence, and accepts
either verdict as long as the exit code matches it. The production 1.25x
limits are unchanged; the verdict unit tests gain fixed-timing cases for
a wall-only regression at CPU parity and a wall-only slowdown just under
the limit.
Fixes CHI-481
0 commit comments