Add cgo dependency to avoid go fmt failures #600
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `PR Check` GitHub Action runs `go fmt` and then builds and unit tests. But the `go fmt` run is currently failing with the error message: ``` package github.com/sijms/go-ora/examples/kerberos: C++ source files not allowed when not using cgo or SWIG: kerberos.cpp ``` This change adds a dummy cgo dependency in the example to make this error go away and unblock the PR checks. The PR checks will continue failing for now, however, because some unit tests themselves are failing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
PR CheckGitHub Action runsgo fmtand then builds and unit tests. But thego fmtrun is currently failing with the error message:This change adds a dummy cgo dependency in the example to make this error go away and unblock the PR checks. The PR checks will continue failing for now, however, because some unit tests themselves are failing.