istioctl describe: fixes, test case, remove deprecated code#20169
istioctl describe: fixes, test case, remove deprecated code#20169esnible wants to merge 13 commits intoistio:masterfrom
Conversation
| framework.NewTest(t). | ||
| RunParallel(func(ctx framework.TestContext) { | ||
|
|
||
| ctx.NewSubTest("ISTIOCTL"). |
There was a problem hiding this comment.
| ctx.NewSubTest("ISTIOCTL"). | |
| ctx.NewSubTest("istioctl"). |
There was a problem hiding this comment.
actually just remove the subtest entirely
|
|
||
| podID, err := getPodID(a) | ||
| if err != nil { | ||
| t.Fatalf("Could not get Pod ID: %v", err) |
There was a problem hiding this comment.
this needs to be the same thing that was passed to the func the tests runs in (ctx in this case)
There was a problem hiding this comment.
I don't understand the comment. What is the problem?
There was a problem hiding this comment.
See the test failure: testing.go:864: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test
You can't use the parents t, its not a valid use of the go testing library
|
@howardjohn Test question. The integration test works locally, and works for the pilot integration tests, but fails for integ-new-install-k8s-tests_istio because for that test I am not sure what to do. I don't want to relax the output comparison because if it changes I want this test to pick it up. I don't know how to recreate locally the options used for integ-new-install-k8s-tests_istio, or why Pilot's /debug/authenticationz?proxyID will return different values when I use it. |
|
@esnible that test is just running |
|
LGTM overall. Will add final approval after John's test comments are addressed. |
|
/test integ-pilot-k8s-tests_istio |
|
@ayj I have completed the things @howardjohn asked for. Please review now. |
|
This is the only reason we have a fair amount of legacy junk in Pilot, will be useful to get rid of this |
|
@nmittler can you take a look? Then we can clean up the config store a bit |
) * istioctl describe: fixes, test case, remove deprecated code * Remove unneeded subtest structure * Remove unnecessary change in describe * Match describe output by regexp, not string * Additional output to test the tests * Keep constructor signature * Fix compilation problem * Look for Envoy config metadata in Istio 1.5.x format * 'make format' * Ran 'gen'
) * istioctl describe: fixes, test case, remove deprecated code * Remove unneeded subtest structure * Remove unnecessary change in describe * Match describe output by regexp, not string * Additional output to test the tests * Keep constructor signature * Fix compilation problem * Look for Envoy config metadata in Istio 1.5.x format * 'make format' * Ran 'gen'
) * istioctl describe: fixes, test case, remove deprecated code * Remove unneeded subtest structure * Remove unnecessary change in describe * Match describe output by regexp, not string * Additional output to test the tests * Keep constructor signature * Fix compilation problem * Look for Envoy config metadata in Istio 1.5.x format * 'make format' * Ran 'gen'
|
@howardjohn What is needed to proceed on this? |
|
@esnible I am pretty sure the code changes were merged but somehow the PR is open, so Ithink we can just close this? |
|
Just verified the changes are in, so I recommend just closing |
|
@esnible @howardjohn do we know how these changes got committed? Maybe someone force pushed from the command-line to the master branch accidentally? I wouldn't expect that would even be possible. |
|
It was actually prow that merged based on the commit log. Apparently the
prow logs looked normal so the assumption it was a github issue. The same
happened to my PR as well and I definitely didn't force push since I wasn't
around when it happened
…On Tue, Jan 21, 2020 at 8:37 AM Nathan Mittler ***@***.***> wrote:
@esnible <https://github.com/esnible> @howardjohn
<https://github.com/howardjohn> do we know how these changes got
committed? Maybe someone force pushed from the command-line to the master
branch accidentally? I wouldn't expect that would even be possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20169?email_source=notifications&email_token=AAEYGXJYZ6UH57PHCX7AI6LQ64QEFA5CNFSM4KGXRJK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQMLAA#issuecomment-576767360>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXKTXRG3RGE2T5MO6T3Q64QEFANCNFSM4KGXRJKQ>
.
|
|
Please rebase this PR. It looks like github only merged some of the commits (3 of 13)? |
|
Closing because this is already merged! 926a1bf#diff-f4fb5eb2363cca54308accde8f31be9c is the commit. |
|
thanks |
Fixes
istioctl x describerecent bugAdds an integration test for
istioctl x describeRemove deprecated
istioctl getputdeletecreateset-contextFixes #18972
Fixes #20157