Update Go to 1.17.4, replace io/ioutil with io, and update golang.org/x/sys - #3041
Conversation
Looks like we need to set some |
e0ae0b4 to
d3078cd
Compare
Codecov Report
@@ Coverage Diff @@
## master #3041 +/- ##
==========================================
- Coverage 62.29% 62.15% -0.14%
==========================================
Files 155 155
Lines 24533 24533
==========================================
- Hits 15283 15249 -34
- Misses 7656 7686 +30
- Partials 1594 1598 +4 |
|
@thaJeztah @crazy-max CI is green! |
|
@thaJeztah I've rejigged the commits, PTAL :) |
455868b to
4dc6dfe
Compare
|
Looks like there is flake: it's green after a re-run... |
|
Yes, I think it's a flaky test; I restarted CI earlier, and looks green again now 👍 |
thaJeztah
left a comment
There was a problem hiding this comment.
LGTM (not a maintainer though)
|
@dperny @tonistiigi PTAL |
|
@thaJeztah I think we need to also upgrade |
|
Ah, yes, we should probably update that as well, although (IIRC), it only affects macOS, so not directly a huge concern in this repository (so I'd be OK with doing it separately) |
|
I tried this: but vndr seems to revamp quite a few things... I suppose I can split the commits, but separate PR is probably needed, as this changes more than was regionally foreseen. |
|
Yes, let's do it separate to not overload this PR too much |
Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
|
@thaJeztah I forgot |
|
Hmm... looks like the DCO bot is not running in this repository; let me try if we can enable it |
|
oh, hm.. don't have access to the repository settings; perhaps @justincormack is able to help 🤔 |
thaJeztah
left a comment
There was a problem hiding this comment.
LGTM
(DCO messages look good)
|
It turned out that accidental changes were somehow to do with my setup, so I'm adding another commit here to update |
…r Go 1.17) Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
|
It hits |
|
cc @tonistiigi |
|
let me try close/reopen to kick CI, and to see if the DCO bot also gets kicked |
|
hm.. ok; it runs on #3042, but doesn't get triggered here 😞 |
|
@thaJeztah Looking at the events that bot listens to, |
Hm.. yeah, that would explain it; perhaps that's part of the bug it previously had, where it got added to all existing pull request, but never got started. Wondering how to add the bot and make it run on all PRs (including existing ones) 🤔 |
No description provided.