-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
ci: Upgrade to Go 1.15 #3642
ci: Upgrade to Go 1.15 #3642
Conversation
5fec9ba
to
a3c8f36
Compare
@mholt I was just curious whether we could try CI on unstable Go versions, and it seems to work... but the tests fail:
Is this something we can fix while keeping backwards-compat? |
The binaries aren't much smaller - 2.5MB on linux, 3MB on mac, 2MB on windows. 🤔 |
Should be? Just looking from the error message it comes from a file that appears to use the unsafe package, so there's probably some voodoo that needs updating. @marten-seemann would know! I'm sure they'll support Go 1.15 once it's released...
40 MB to 2.5 MB? Not bad! 😋 j/k... I suppose you meant size delta. 2.5 MB less for free (well, by simply upgrading Go) is pretty good! |
@marten-seemann Would you be able to ping us when there's a new release that's compatible with Go 1.15? (We're getting test failures on Go 1.15 in the quic-go lib) Go 1.15 was only released an hour ago -- there's no hurry. :) |
@mholt Yes, definitely. Will be some time later this week. I was planning to cut a new release of quic-go soon anyway - there've been a bunch of bug fixes and - which is important for Caddy - improvements to the QPACK compression efficiency. |
482aa9a
to
b162098
Compare
Thanks @marten-seemann! I think that issue looks to be fixed with the latest release. There is this new test failure though:
|
Cool, that error is a new feature of the Go 1.15 compiler. Anyway, thanks Marten and Francis! |
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.
Great work on this, thanks again both of you!
No description provided.