Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #83 +/- ##
=======================================
Coverage 73.10% 73.10%
=======================================
Files 7 7
Lines 714 714
=======================================
Hits 522 522
Misses 162 162
Partials 30 30 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| with: | ||
| go-version-file: '${{ github.action_path }}/go.mod' | ||
| env: | ||
| CGO_ENABLED: 0 |
There was a problem hiding this comment.
There was a problem hiding this comment.
Yeah I think that makes sense.
$ git grep -i cgo
Dockerfile:RUN CGO_ENABLED=0 ./bashbrew.sh --version; \
Dockerfile.release:ENV CGO_ENABLED 0
action.yml: CGO_ENABLED: 0There was a problem hiding this comment.
Ok, now moved to bashbrew.sh. We could drop it from the Dockerfile but it seems fine to be explicit there and in the Dockerfile.release.
$ git grep -i cgo
Dockerfile:RUN CGO_ENABLED=0 ./bashbrew.sh --version; \
Dockerfile.release:ENV CGO_ENABLED 0
bashbrew.sh:: "${CGO_ENABLED:=0}"
bashbrew.sh:export GO111MODULE=on CGO_ENABLEDDisable cgo to fix build failure on GHA windows-2022
5eb555b to
c4273aa
Compare
|
Is there a reason to disable for all rather than just for |
|
Just for consistency across OS, architecture, and build pipeline. It was already disabled for the builds using |
Disable cgo to fix build failure on GHA
windows-2022Example failure from PRs to official-images: