Stabilize JDK 10 Java CI - #200
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe pull request updates JDK 10 CI test execution and failure artifact collection. It also changes the search priority for CJK system fonts when font subsetting is disabled. ChangesJDK 10 CI
CJK font search order
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to No concrete issue remains that should block merging. Font coverage on the JDK 10 runner remains unverified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Summary
Root cause
The obsolete HotSpot 10 runtime is unstable in compiled mode across heterogeneous hosted-runner CPUs. Changing vendors, retrying, disabling container detection, and changing Surefire launch modes did not make compiled execution reliable. Diagnostic runs also exposed incomplete Simplified Chinese extraction when GNU Unifont was selected as the primary non-subset fallback.
Maven remains on JDK 17 so normal packaging and shade verification are unchanged. Only the JDK 10 test fork uses
-Xint, which removes the unstable JIT path while still running the complete compatibility suite on Java 10.Validation
git diff --check origin/main...HEADSummary by CodeRabbit