Repository navigation
The boundary, root and corpus harnesses run in CI - #1650
Merged
Merged
Conversation
Three of the measurement harnesses move into Sources/Tests/Harnesses as console projects that dotnet test does not pick up, and .github/workflows/Harnesses.yml runs them on every change to the library, one step each, uploading their reports. Each fails on a defect and on nothing else: - BoundCheck: any value Simplify changes at a boundary point. - RootCheck: a missing root, a returned value that is not a root, an exception. - CasBench: a wrong answer, an exception. An unsolved problem is coverage. A timeout fails none of them, since a shared runner is slower than the machine a budget was set on. All three are clean on master, together in about six seconds. A report goes to HARNESS_REPORTS when that is set, otherwise beside the projects, where git ignores it, and names the commit it measured. Part of #1256. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura
This was referenced Oct 1, 2026
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
1 participant
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.
#1256 asked whether the property harnesses should live in this repository, and you moved it to 2.6.0, which I read as yes. This is the first part: the three harnesses whose criterion is already "a defect, and nothing else".
BoundCheckSimplifykeep the value at the boundary: across a branch cut, off the real line, outside a principal interval, at a poleRootCheckCasBenchSources/Tests/Harnesses, as console projects besideAotSmokeTest. They are not in the solution anddotnet testdoes not pick them up..github/workflows/Harnesses.ymlruns them on every change underSources/AngouriMath, one step each, so a red run names the harness. It uploads their reports either way.HARNESS_REPORTSwhen that is set, and otherwise beside the projects, where git ignores it.Measured on master
e8446b65:BoundCheck948 shapes and 0 disagreements;RootCheck596 of 596 clean;CasBench120 of 121 solved, 0 wrong. They take about six seconds together, all exit 0, and the reports namee8446b65.Negative control: with one expected limit made wrong in
CasBench's corpus, it exits 1. It was reverted before committing.CLAUDE.mdsaid every harness lives outside the repository, and now names these three.The rest come in later parts, as each gains a criterion that fails on a defect rather than on a known finding.
canoncheck,confluenceandpropcheckreport known findings today, so they need a recorded baseline, the way the corpus gate records verdicts.crashcheck,simpsweep,rulecheckandegraphtake one to four minutes each, which is more a nightly job than a per-change one.Part of #1256.
🤖 Generated with Claude Code
https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura