Skip to content
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

[release-3.4]: Pin go version in go.mod to 1.12 #12839

Merged
merged 4 commits into from
Apr 7, 2021

Conversation

lilic
Copy link
Contributor

@lilic lilic commented Apr 7, 2021

As go 1.12 is what is tested in CI as well as recommended to be built
with 1.12 we should also pin to this in the go directive version of go.mod file.

Fixes #12838.

As go 1.12.2 is what is tested in CI as well as recommended to be built
with 1.12.2 we should also pin to this in the go directive version.
@lilic
Copy link
Contributor Author

lilic commented Apr 7, 2021

I tried to follow the contributing guide around the commit msgs, let me know if there is anything incorrect, happy to make the needed changes!

@ptabor ptabor self-requested a review April 7, 2021 13:44
@lilic
Copy link
Contributor Author

lilic commented Apr 7, 2021

Not sure I understand the e2e test failures, any hints at what I could look at? 🤔

@ptabor
Copy link
Contributor

ptabor commented Apr 7, 2021

3.4 are pretty flaky. A lot of improvement in 3.5 tests.

Adding created by testing.runTests.func1 to

if stack == "" ||

will at least eliminated one of the 'flakes.

@lilic
Copy link
Contributor Author

lilic commented Apr 7, 2021

A lot of improvement in 3.5 tests.

Nice to hear that! 🎉

Thanks for the suggestion! Do you want me to include that in this PR?

@ptabor
Copy link
Contributor

ptabor commented Apr 7, 2021

Yes - let's try to add this commit -> and this will retrigger the tests. Maybe we will get lucky.

@ptabor
Copy link
Contributor

ptabor commented Apr 7, 2021

Thank you for the fixes.

@ptabor ptabor merged commit b7e5f5b into etcd-io:release-3.4 Apr 7, 2021
@lilic lilic deleted the fix-go-version branch April 7, 2021 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants