ci: run stdlib corpus gate across Go versions#9
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Good approach to close the older-stdlib coverage gap. Two things to address: (1) the |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9 +/- ##
=======================================
Coverage 32.44% 32.44%
=======================================
Files 41 41
Lines 12640 12646 +6
=======================================
+ Hits 4101 4103 +2
- Misses 7806 7809 +3
- Partials 733 734 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Run the stdlib asm corpus gate across the same Go version range already covered by the
go testmatrix, and run that gate on both CI host platforms we care about:ubuntu-latestandmacos-latest.Why
The existing workflow only ran
scripts/check-stdlib-corpus.shunderGo 1.26.xon Ubuntu.That left an older-stdlib gap: code paths exercised by LLGo demos under
Go 1.21.13could still pull in asm syntax that the current corpus gate never checked.This change makes that gap explicit by adding a dedicated
stdlib-corpusmatrix job.What changed
buildas the single-versionGo 1.26.xbuild job.stdlib-corpusmatrix job for:ubuntu-latestmacos-latest1.21.x1.22.x1.23.x1.24.x1.25.x1.26.xlinux/amd64linux/arm64darwin/amd64darwin/arm64Local verification
GOTOOLCHAIN=go1.26.1 ./scripts/check-stdlib-corpus.shGOTOOLCHAIN=go1.21.13 ./scripts/check-stdlib-corpus.shlinux/amd64