Repository navigation
test(analysis): drop the known marks #1207 made stale - #1220
Conversation
Buffer's fix lets a long line and polygons agree with the reference, and the test fails on a marked case that agrees. The point and road cases still differ, within their looser tolerance, so they keep theirs.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Remove buffer case overrides crates/analysis/tests/reference/cases.json, crates/analysis/tests/reference/generate.py |
The long-line, outward polygon, and inward polygon cases no longer use the known-issue metadata or tolerance override. Their expected tolerance remains 0.001. |
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Other
Possibly related issues
- [Bug]: Buffer outlines sit up to 10 % of the distance off: long sides come back from the plane straight, and arcs have 32 edges #1159 — Identifies inaccurate buffer outlines and the reference cases updated here.
Possibly related PRs
- opengeos/RustGIS#1161 — Added the buffer reference cases and their known-issue metadata.
- opengeos/RustGIS#1207 — Changed buffer outline generation for the cases whose known-issue marks are removed here.
Suggested reviewers: mavrick-f
Merge Risk: 
Minimal · up to 6fbc6
-
The three buffer cases return to strict reference comparisons. No actionable merge-blocking risk is identified; merge after normal checks pass.
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Title check
-
Explanation
The title "test(analysis): drop the known marks
#1207made stale" names the main change: removing outdatedknownmarks from buffer test cases. It is specific and matches the changeset, which removes those marks from generate.py and cases.json. It names the test scope and the cause, so a teammate scanning history understands the primary change.
Full details: Description check
-
Explanation
The description follows the repository template in substance. It covers the cause, the fix, and the evidence. It explains why the three marks were removed and why the other three marks remain. The template's Summary is covered by the Cause and Fix sections. The Testing section is covered by the Evidence section, which describes a failing run on clean origin/main and a passing run with the change, but it does not name a command such as
cargo xtask ci. The UI evidence section is omitted, which is acceptable because the change has no visible UI effect. The Related issue section is not explicit: it refers to#1207and#1161and to closed issue#1159, but it lacks a "Closes" or "Part of" line for the PR itself.
-
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 1 files.
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
-
Finishing Touches
-
Generate docstrings
-
- Commit to this branch
- Create a new PR
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the lines with care
Three buffer marks are no longer there
The tolerance stays in place
The cases keep their expected pace
Hop, the reference tests compare!
Code reviewBugs: None found. The PR removes three
Security: None. The change is test fixtures and a generator tweak. Performance: None. Quality:
AGENTS.md: No violations. The test change needs no crash regression test, and no copyleft code or assets are involved. Not verified: I could not run Change sizeCompared: the whole PR against main (merge base 78b1799 to PR head 6fbc655).
|
📖 Docs preview
GitHub Pages takes a minute or two to publish a new commit. |
Keeps his resolution of the shortcut editor's fields; brings in opengeos#1220. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cause: #1207 fixed Buffer's outlines, so
buffer a long line,buffer polygonsandbuffer polygons inwardnow agree with the reference.tools_agree_with_the_referencefails on any case that agrees while still carrying aknownmark. #1207 was tested before #1161 added those marks to main, so the conflict only appeared once both had landed, and every PR'stest / Test (ubuntu-latest)fails on it.Fix: remove the three marks from
generate.pyandcases.json. Their strict tolerance now applies, so a regression there fails the test.Evidence: the test failed on a clean
origin/main(78b1799) with those three messages, and passes with this change.Left as it is:
buffer points,buffer points farandbuffer linesstill differ from the reference by about 6e-3 and 1e-3 of their area, inside the 10 % bound, and keep their marks. Those marks name #1159, which is closed, so they need a new issue or a fix of their own.Summary by CodeRabbit