-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Update to golang 1.15.2 #4050
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
Update to golang 1.15.2 #4050
Conversation
|
Build succeeded.
|
|
Seeing some failures; |
b0d1d74 to
19e885c
Compare
|
Build succeeded.
|
19e885c to
05db255
Compare
|
Build succeeded.
|
05db255 to
fa88c1e
Compare
|
Build succeeded.
|
fa88c1e to
4bae9b2
Compare
|
Build succeeded.
|
|
As a headsup, the etcd/bbolt library is having a checkptr failure which is currently being hit in the current containerd test suite with go 1.14. |
|
I have built |
|
@Foxboron what was the test failure? |
|
Note I have removed the non-failing tests from the output to shorten it a bit. |
|
@Foxboron I cannot reproduce the issue on my environment (Go 1.14 + Debian 10 + EC2 m5d.metal). There was a similar report on golang-nuts but the cause of the issue was the machine didn't have enough memory to run tests with ThreadSanitizer. |
|
@kzys Can you triple check that the tests are run with |
|
@Foxboron Thanks. I thought it was default. But |
4bae9b2 to
f9397d1
Compare
|
Build succeeded.
|
f9397d1 to
4f33893
Compare
|
Build succeeded.
|
4f33893 to
ea0b79c
Compare
|
Build succeeded.
|
Codecov Report
@@ Coverage Diff @@
## master #4050 +/- ##
=======================================
Coverage 38.34% 38.34%
=======================================
Files 90 90
Lines 12728 12728
=======================================
Hits 4881 4881
Misses 7181 7181
Partials 666 666
Continue to review full report at Codecov.
|
ea0b79c to
3789c4d
Compare
|
LGTM 👍 |
|
We need to make sure that this doesn't cause the problem described in #4509 |
|
I could not reproduce the issues unless I built the shim with |
|
@cpuguy83 Just checking, but are you running from HEAD? I can't reproduce this from master, so I think it's been fixed after the |
|
@Foxboron The issue is specifically with how you build it. I built from HEAD, but adding |
|
The Makefile should build without that, correct? Line 195 in d43d546
|
|
Yes, the makefile builds correctly. |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
32eb611 to
d1c8d98
Compare
|
Updated to Go 1.15.2 |
|
Build succeeded.
|
cpuguy83
left a comment
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.
LGTM
One thing to note... and I'm not sure if there is somewhere to put this... but clients doing signal forwarding will see a lot of SIGURG as noted in #4532 which ignores SIGURG for ctr
opening as draft, to see if there are regressions/failures
temporarily rebased on #4072