Repository navigation
feat: human-friendly dashboard reports for cron summary issues (#432) - #433
Merged
Merged
Conversation
Every section was titled `## cron-<kind>` with the scope only in a hidden marker, runs were bare undated URLs, a finding said `lost` without the previous value, and the body was rewritten silently — no notification, no history, and no previous report to compare with since the `results` tip is rewritten each run. Each scope section now names the scope (a stable anchor for the table of contents regenerated on top), shows its `note`, links the run, the scope report and the previous run, and keeps a bounded history fed by the same finding diff that posts a comment. Finding rows show before → after.
The live run showed three gaps: the `note` was inlined into the bash script, so its backticks ran as a command substitution (env var instead); a missing-report row produced a `problem=workflow` reproduce hint; and sections written by the older report had no `cron-status` marker, so the table of contents ignored their findings until their scope ran again — rows are now counted from the tables themselves.
…rts (#432) - Restructure the issue with an explanatory pedagogical header and an Overall Scope Status dashboard table linking each scope directly. - Scope sections now carry human-readable titles (e.g. 'JuMP — Solver Robustness'), an explicit Focus and Cadence description, and clean badges for status. - New summary issues pre-populate all known scopes so the full test landscape is visible from day one. - Findings tables format outcomes clearly (e.g. 'converged → not_converged') and provide an actionable 'How to investigate' details block with copy-pasteable Julia reproduction commands and direct data links. - Tests updated to verify the new report layout and lifecycle.
…are clean Unlike failure or draft tracking which only need an issue when an action is required, the convergence report acts as an ongoing dashboard tracking status across all scopes.
ocots
changed the title
…and all-clear logic (#432)
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.
Summary
Closes #432.
Replaces the raw, repetitive issue bodies with human-friendly, pedagogical dashboard reports that make it effortless for developers and maintainers to understand solver convergence and regressions at a glance.
Key improvements
Pedagogical Header & Clear Guidance:
⚠️) appears (how to reproduce, check data files, verify legitimate solver/guess changes).Overall Scope Status Dashboard Table:
✅ Clean,⚠️ N findings, or*Awaiting run*).Contextualized Scope Sections:
## JuMP — Solver Robustness,## JuMP — Nominal Convergence).resultsbranch, and the previous run for comparison.Actionable Investigation Block:
using Pkg; Pkg.test(...)).problems/<problem>/result.json), the run report, and theenv/Manifest directory.converged → not_converged, relative objective shifts, new solutions).Bounded History & Notifications:
<details>Recent history</details>log of the last 10 changes per scope across runs.Test plan
python3 -m unittest discover -s tools/cron/test -p 'test_*.py' -v— 31 tests passing (units, mocks, integration).Generated with Devin