Tests on main are failing - #304
Closed
1-Bort-1 wants to merge 1 commit into
Closed
Conversation
1-Bort-1
commented
Sep 11, 2026
1-Bort-1
left a comment
Contributor
Author
There was a problem hiding this comment.
Independent review (advisory)
Verdict: APPROVE · 0 inline, 0 off the diff
Good
- The diff is exactly one line and matches the PR card: it rewords the misleading comment to state the truth about the 1e-8 step.
- The new comment follows §3/§5: it is one line, states a non-obvious fact at the spot it bites, and contains no history, rationale, or negation of a previous version.
- Scope is correct: +1/-1 in the test file the base PR already touched; no public symbols, no docstrings, no dependencies, no generated files.
opencode, rubric CLEAN_CODE.md. A different lab from the implementer
on purpose: a reviewer sharing its blind spots would not flag its mistakes.
Contributor
Author
|
Local full suite: FAIL (7 min, Julia 1.12.7, one cell of the matrix) |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Sep 11, 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
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.
TL;DR
Tests on
mainare red because thePOLAR_MATRICESforwarddiff check intest/solver/test_forwarddiff.jlflakes when a finite-difference step spans a knot of the polar's 5° alpha grid. #292 carries the fix; this PR sits on top of it and clears the advisory review's one comment, the misleading step-width comment.What is failing and why
mainCI failed the "AutoForwardDiff matches AutoFiniteDiff (LOOP, POLAR_MATRICES)" testset twice with the identical assertion:Expression: rel_err < 0.001/Evaluated: 0.04001429189872729 < 0.001attest/solver/test_forwarddiff.jl:88— run 34446797250 (the merge of #285) and again on release PR #302 (run 34628824540). Nothing else onmainfailed.The check differentiates a piecewise-linear polar whose alpha grid has knots every 5°, and a 1e-5 forward-difference step straddling a knot measures the average of two slopes while forward AD takes one. Whether a panel's converged alpha lands inside that window is decided by the NeuralFoil fixture, which is redrawn every CI run (#291) — that is the #287 flake, and the recorded failure value matches #292's knot-bisection exactly.
What changed
#292 (the base of this stack) fixes the flake in
test/solver/test_forwarddiff.jlonly:rtol1e-7→1e-11 so the converged panel alpha stops wobbling, the finite-difference step 1e-5→1e-8 so the secant stays inside one polar cell, and the bound 1e-3→1e-4 — a tightening, not a loosening. Its CI is green.This PR is the one commit on top: #292's advisory review flagged the added comment at line 83, which described the old wide step next to the new narrow one and could invert the intent for the next reader. Reworded to say what is true:
# 1e-8 keeps the secant inside one cell of the polar's 5° alpha grid.The test result is untouched.Left alone: the fixture-reproducibility root cause is #291, and the release is #302 — neither belongs to this stack.
Verification
mainCI run 34446797250 and release Release VortexStepMethod v5.1.0 #302 run 34628824540 both failrel_err < 0.001/Evaluated: 0.04001429189872729 < 0.001attest/solver/test_forwarddiff.jl:88test/solver/test_forwarddiff.jlgreen on the stacked branch (juliaserver,testenv, 7/7) and green on unpatchedmainlocally (7/7 — the flake only bites on a fresh fixture draw, so the recorded CI value is the reproduction)agent ci-localrunning · GitHub CI: pending PR openScope
+1 / −1 in
test/solver/test_forwarddiff.jland nothing else. Stack: 2/2 → #292.Closes #303 · task
VortexStepMethod.jl-303