Repository navigation
ci(benchmarks): a published result records specsolve's release version rather than 0.0.1 - #2043
Merged
Merged
Conversation
…e refuses a workflow that does not An apostrophe inside a single-quoted description made the file unreadable, so GitHub saw no workflow_dispatch trigger and the trigger:published-bench label's dispatch failed with HTTP 422. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTByC5UJJWvcFj3mvmv83v
…n rather than 0.0.1 The measuring job checked out one commit with no tags, so the version counted from no tag. A full checkout gives 0.9.1.dev34+g61172a8af where a depth-1 one gives 0.1.dev1+g61172a8af. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTByC5UJJWvcFj3mvmv83v
FBumann
enabled auto-merge (squash)
October 14, 2026 20:24
Merging this PR will not alter performance
Comparing Footnotes
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
The following content was generated by AI.
The measuring job checked out one commit with no tags, so every published result records specsolve as
0.0.1.dev1+g<sha>.fetch-depth: 0on that checkout gives the version counted from the nearest tag.Cause, verification, and what is not done
The eight files on
mainfrom #2039 all say0.0.1.dev1+gfbc735a5b; the lock installs0.9.1.dev31+gfbc735a5b. The version comes from hatch-vcs ([tool.hatch.version] source = "vcs"), which needs the tags and the history back to the nearest one.Reproduced on
mainat61172a8, with setuptools-scm:actions/checkoutdoes by default)0.1.dev1+g61172a8af0.9.1.dev34+g61172a8afci.ymlalready usefetch-depth: 0.tests/test_architecture.py -k workflow, 13 passed. Not run:pixi run check, and a real run on the box._same_installmatches on the commit and ignores the release number. So nothing failed and nothing here changes it.mainkeep0.0.1.dev1until the next published run. Measured files are not edited by hand.fbc735a(closed test(ci): the published-benchmark workflow parses again, and the suite refuses a workflow that does not #2038, already inmainthrough docs(benchmarks): the published benchmarks are re-measured at the new model sizes, five times each tenfold step #2039) so the push was a fast-forward; the diff againstmainis the one line.Type
ci: the diff touches only.github/, so no changelog line.🤖 Generated with Claude Code
https://claude.ai/code/session_01NTByC5UJJWvcFj3mvmv83v
Generated by Claude Code