Repository navigation
docs(inflight): flaky @StandardException build finding + release-mechanics update - #60
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
❌ Duplicate Code ReportTwo engines run in parallel for cross-validation. Each has its own thresholds tuned to its baseline - the real safety net is the per-engine "max increase vs base" check. ✅ PMD CPD
No new clones introduced by this PR. ❌ jscpd (language-agnostic)
No new clones introduced by this PR. Powered by astubbs/duplicate-code-cross-check |
✅ SpotBugs ReportNo bugs found (new bugs only — baseline from base branch excluded). |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #60 +/- ##
============================================
- Coverage 77.15% 77.08% -0.08%
- Complexity 75 1153 +1078
============================================
Files 82 82
Lines 4190 4190
Branches 386 386
============================================
- Hits 3233 3230 -3
- Misses 765 768 +3
Partials 192 192
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Add the intermittent Lombok @StandardException annotation-processing compile failure to the CI reliability section — a required-gate (Unit Tests) flake, distinct from the Integration/TestContainers flake already noted, that also caught the release pipeline's maiden publish run. (The release-mechanics rewrite this commit originally carried is already on master via other work, so it's dropped in the rebase — this now just adds the finding.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3d0bc9a to
377d322
Compare
❌ Mutation Testing (PIT) ReportPIT did not produce a report. Most commonly this means a test failed in the baseline (PIT runs all tests unmodified first to establish green) and PIT aborted before mutating. See the "Run PIT mutation testing" step logs for the failing test, then either fix it or add it to |
Adds the flaky-build finding to
docs/inflight.mdand refreshes the now-stale release-mechanics note.@StandardExceptionannotation-processing compile failures on master - non-deterministic, and the recentlogback 1.6.0bump build (run 30311773374) failed on it (logback is a red herring -testscope). Risk: the release pipeline gates publish on a green build, so flaky-red = intermittent publish failures. Fix direction: harden the exception-class constructors (@StandardException+ custom vararg ctor footgun).Docs only.
🤖 Generated with Claude Code