travis: also test go-fuzz with Go tip (including because oss-fuzz is using tip) #239
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.
In travis, add tests for Go tip on linux and osx.
In tip and Go 1.13,
GO111MODULE
defaults toon
(whereas it defaults toauto
in 1.11 and 1.12).However, travis explicitly sets
GO111MODULE=auto
. Therefore, when testing tip, we explicitly setGO111MODULE=on
to give normal tip / 1.13 behavior.Note: it does not work just to use
env: GO111MODULE=on
because thengo get
stops working (perhaps becausego-fuzz
is not yet a module). Instead, we useSET_GO111MODULE
in the travis configuration, and then check that to know whether or not to doexport GO111MODULE=on
just before invokinggo-fuzz-build
andgo-fuzz
.Separately, pull request #237 was merged, but that current fix is probably incomplete for disabling modules. With these changes, travis passes with 1.11 and 1.12, but currently fails on tip with:
Updates #237
Updates google/oss-fuzz#2188