ci: harden Go Windows linker setup#49
Conversation
Signed-off-by: Will Killian <wkillian@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
🧰 Additional context used📓 Path-based instructions (2)justfile📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)
Files:
{.github/**,.gitlab-ci.yml,.pre-commit-config.yaml,justfile,scripts/**}⚙️ CodeRabbit configuration file
Files:
🔇 Additional comments (1)
WalkthroughThe ChangesOS Detection and Windows Configuration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 8/10 reviews remaining, refill in 11 minutes and 2 seconds. Comment |
Overview
Harden the Go binding CI recipe so Windows jobs reliably select the clang/lld linker path when GitHub-hosted runner shell metadata changes.
Details
RUNNER_OS,OSTYPE, oruname -sinstead of relying only onOSTYPE.-fuse-ld=lldbehavior so Go does not fall back to MinGW GCC for the MSVC-built FFI library.Where should the reviewer start?
Start with
justfile, specifically thetest-gorecipe's Windows detection and linker setup.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit