-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add windows servers to smoke test #83
Conversation
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. @@ Coverage Diff @@
## master #83 +/- ##
=======================================
Coverage 73.10% 73.10%
=======================================
Files 7 7
Lines 714 714
=======================================
Hits 522 522
Misses 162 162
Partials 30 30 |
action.yml
Outdated
@@ -11,6 +11,8 @@ runs: | |||
- uses: actions/setup-go@v3 | |||
with: | |||
go-version-file: '${{ github.action_path }}/go.mod' | |||
env: | |||
CGO_ENABLED: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we instead add this to
Line 9 in 6334a4f
export GO111MODULE=on |
(with : "${CGO_ENABLED:=0}"
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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_ENABLED
Disable 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-2022
Example failure from PRs to official-images: