Update k8s.io/test-infra dependency and fix GCP Mason#2447
Update k8s.io/test-infra dependency and fix GCP Mason#2447istio-testing merged 1 commit intoistio:masterfrom
Conversation
|
😊 Welcome @ixdy! This is either your first contribution to the Istio test-infra repo, or it's been You can learn more about the Istio working groups, code of conduct, and contributing guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
Hi @ixdy. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
5d6d287 to
89478f8
Compare
|
/ok-to-test |
|
I additionally needed to update some unrelated files, since some Prow internal data structures have changed. |
Thanks! Additionally, can you run |
|
it looks like it's unhappy about licenses, and I have no idea how to fix this: |
I am not entirely certain either. It is either a bug with the license resolution logic or an issue with the dependencies. Related discussion: istio/istio#20379. @howardjohn or @sdake any idea how to resolve? |
|
ok, I think I've fixed some of these issues by pinning to newer versions (which include the LICENSE files), though a bunch are still failing; I suspect they'll need to be whitelisted: Going one-by-one:
|
|
All of the third-party dependencies under tektoncd/pipeline are already whitelisted, just not with their third-party paths. I'm not sure whether the tool should be taught to recognize this, or if we should whitelist them explicitly. Any guidance on what I should do about the other dependencies? |
Whitelisting those specific modules should be fine. |
|
I am no expert, but I don't think k8s can/should depend on it either...
Unless it's different due to CNCF
…On Fri, Mar 6, 2020 at 4:55 PM Travis Clarke ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In licenses/github.com/otiai10/curr/LICENSE
<#2447 (comment)>:
> @@ -0,0 +1,5 @@
+Copyright © 2015 Hiromu OCHIAI ***@***.***>
+
+This work is free. You can redistribute it and/or modify it under the
+terms of the Do What The Fuck You Want To Public License, Version 2,
Can we drop the dependency?
This if from kubernetes/test-infra. I am not sure removing it is an
(easy) option.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2447?email_source=notifications&email_token=AAEYGXPZMED4GN44EBED2W3RGGLOZA5CNFSM4K6H7NBKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCYMICLI#discussion_r389208821>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXLFONWB7VORI6AODK3RGGLOZANCNFSM4K6H7NBA>
.
|
|
I'm trying to understand where this dependency is coming from, but I'm failing. Nothing in |
|
I have not traced it all the way but it is from |
|
Ahh thats right... we have had this problem before. K8s license checker checks code it uses from vendor, which is pruned, whereas istio's is checking all transitive dependencies by github.com/tektoncd/plumbing > github.com/google/go-licenses > github.com/otiai10/copy > github.com/otiai10/mint > github.com/otiai10/curr I don't know what we do now. |
|
I opened otiai10/curr#2. We'll see if the maintainer is willing to switch the license. |
|
oh, this is going to need me to re-run |
Additionally, update (and pin) - github.com/otiai10/curr - github.com/otiai10/mint - github.com/pelletier/go-buffruneio
|
ok, looks like this is hopefully set once istio/common-files#206 gets in. |
|
thanks! sorry for the license issues. the common files update should automatically get merged in here in a bit |
|
/retest
should work without rebase
…On Sat, Mar 7, 2020, 11:31 AM Travis Clarke ***@***.***> wrote:
@ixdy <https://github.com/ixdy> - rebase to pull in the new
common/config/license-lint.yml, then I think all is set.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2447?email_source=notifications&email_token=AAEYGXNAJAIX4NLQ24FMNPTRGKOH5A5CNFSM4K6H7NBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOEDQ7Q#issuecomment-596129918>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXNXSLESYYVNXXBVIM3RGKOH5ANCNFSM4K6H7NBA>
.
|
|
ok, the last remaining question: does anything automatically build and publish |
It is currently manual. |
|
can you build and push when convenient? (doesn't need to happen this weekend.) I don't have access to the istio-testing project. |
|
Some recent changes to Boskos changed some of the CRDs slightly, which is now causing older Mason implementations to fail to register:
Thankfully, the changes are fairly straightforward, and we can easily use a caching kubernetes client now, too. (The benefits of caching are probably fairly low, since DRLCs don't change that often.)
Relevant upstream changes for context:
kubernetes/test-infra#16206
kubernetes/test-infra#16249
kubernetes/test-infra#16367