HOLD/DO-NOT-MERGE just see if the standalone key/cert probe has some side effect in CI

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test lint_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test lint_istio

e2e-simpleTestsMinProfile_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test e2e-simpleTestsMinProfile_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

e2e-simpleTestsMinProfile_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test e2e-simpleTestsMinProfile_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

e2e-simpleTestsMinProfile_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test e2e-simpleTestsMinProfile_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

e2e-simpleTestsMinProfile_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test e2e-simpleTestsMinProfile_istio

unit-tests_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

e2e-simpleTestsMinProfile_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test e2e-simpleTestsMinProfile_istio

unit-tests_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test unit-tests_istio

e2e-dashboard_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-dashboard_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

e2e-simpleTestsMinProfile_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test e2e-simpleTestsMinProfile_istio

e2e-dashboard_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-dashboard_istio

unit-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
acb57abf5b8c52ba50bf3f2717b84fc00d1067da
link
/test integ-galley-k8s-tests_istio

lint_istio
8197025e98d64d8e44655a041aa72ac26604dece
link
/test lint_istio

e2e-dashboard_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-dashboard_istio

unit-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test unit-tests_istio

e2e-simpleTestsMinProfile_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-simpleTestsMinProfile_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-dashboard_istio

unit-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test unit-tests_istio

e2e-simpleTestsMinProfile_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-simpleTestsMinProfile_istio

integ-security-k8s-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test integ-security-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@howardjohn @linsun could you take a look of this PR? We need this to be merged in order to unblock https://github.com/istio/istio/pull/18030/files
I think it's better to have separate PR from above, because know we introduce implementation change in pilot agent.
Feel free to appoint other reviewer candidates.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test e2e-simpleTestsMinProfile_istio

integ-security-k8s-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b6560f363c4f07995b563e84035d10b0f5d29e18
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

/test unit-tests_istio --

/test unit-tests_istio

Changed to use existing key/cert  wait logic when auto mTLS is enabled.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test integ-security-k8s-tests_istio

lint_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test lint_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test integ-security-k8s-tests_istio

lint_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test lint_istio

unit-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3772815d39d9732f01f946fdcbbe7cf44f4dca6
link
/test integ-security-k8s-tests_istio

lint_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test lint_istio

unit-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test integ-mixer-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test integ-mixer-k8s-tests_istio

lint_istio
e851578ca5ec2690e15d4dfafbc34a2a202322b5
link
/test lint_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5cec17526ee1fafef81c759cefd64c0c622363a9
link
/test integ-mixer-k8s-tests_istio

lint_istio
e851578ca5ec2690e15d4dfafbc34a2a202322b5
link
/test lint_istio

unit-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test unit-tests_istio

integ-security-k8s-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test integ-security-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: PR needs rebase.

Instructions 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.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test unit-tests_istio

integ-security-k8s-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test integ-security-k8s-tests_istio

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test unit-tests_istio

integ-security-k8s-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test integ-security-k8s-tests_istio

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test integ-security-k8s-tests_istio

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
48136b6bccf56d0bca795cd74ee314b3a732fab9
link
/test integ-security-k8s-tests_istio

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTestsMinProfile_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTestsMinProfile_istio

pilot-multicluster-e2e_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-multicluster-e2e_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTestsMinProfile_istio

pilot-multicluster-e2e_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-multicluster-e2e_istio

gencheck_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test gencheck_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTestsMinProfile_istio

pilot-multicluster-e2e_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-multicluster-e2e_istio

gencheck_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test gencheck_istio

istio_e2e_cloudfoundry_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test istio_e2e_cloudfoundry_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-k8s-tests_istio

integ-pilot-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-security-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-galley-local-tests_istio

integ-istioctl-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioctl-k8s-tests_istio

integ-pilot-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-pilot-local-tests_istio

integ-framework-local-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-framework-local-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

release-test_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-telemetry-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

integ-istioio-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-mixer-no_auth_istio

e2e-simpleTests-cni_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test e2e-simpleTestsMinProfile_istio

pilot-multicluster-e2e_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-multicluster-e2e_istio

gencheck_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test gencheck_istio

istio_e2e_cloudfoundry_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test istio_e2e_cloudfoundry_istio

lint_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test lint_istio

Instructions 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. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-mixer-k8s-tests_istio

integ-new-install-k8s-tests_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test integ-new-install-k8s-tests_istio

pilot-multicluster-e2e_istio
e3c463c11bf476ad1b41f7d77ad4e033d45b02c9
link
/test pilot-multicluster-e2e_istio

integ-telemetry-k8s-tests_istio
11384b7680eb2d80391527fa95572a3448fe1e5e
link
/test integ-telemetry-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
11384b7680eb2d80391527fa95572a3448fe1e5e
link
/test integ-telemetry-k8s-tests_istio

Instructions 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. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new pull request created: #18146


Fix squared optimization steps bug

Currently, when increasing the number of epochs, the number of steps per epoch is also increased, leading to a number of optimization steps thats roughly (examples / batch size) * epochs * epochs instead of (examples / batch size) * epochs. The proposed change should fix this.

Hello!
This bug was discovered https://github.com/huggingface/setfit/pull/268#issuecomment-1382924584, and a fix was proposed. It involves simply removing this line:
https://github.com/huggingface/setfit/blob/f777c2c60b270604dae0dc1db4eea815e8c9019d/src/setfit/trainer.py#L378
When steps_per_epoch is not specified, the number of steps per epoch will be equivalent to the number of datapoints in the dataloader. See the docs on the fit method for more info.
The remainder of the code would not need any changes.
Would you agree that this is a preferable solution over the changes that you have proposed? I think it's best if we make a new PR for this.

Tom Aarsen

Hey @tomaarsen, I removed the argument as you mentioned. Beyond that, this version also fixes the fact that for the triplet losses self.num_epochs was used to calculate total number of optimization steps for reporting when in fact num_epochs should be used because self.num_epochs can be shadowed by an argument to the train method

You're very right! Thanks for catching that. I'll merge this once the tests go green 🎉

Wonderful! Thank you for this fix, and for the editions on the PR @twerkmeister!


Does v17 still needs Zone.js?

Feature Description
Does v17 still needs Zone.js?
Use Case
No response

Yes, there isn't a viable alternative for us at the moment.

@crisbeto : Could you narrow down the range of that moment for us? I.e. months or years? Hard to make decisions on our side if we want to get rid of Zone.js without knowing if we get stuck using material.


Add eWiFiSecurityWPA2_ent into Wi-Fi Security types

Add eWiFiSecurityWPA2_ent into Wi-Fi Security types
Description
This commit adds eWiFiSecurityWPA2_ent into WIFISecurity structure to
let vendor be able to support Wi-Fi WPA2 enterprise security in the
future.
Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@dan4thewin @gkwicker  - For review.

Adding another security type could potentially break our existing test case. An email is sent to the group to exercise the logic. A better approach, along with this change, is to update port specific WiFi implementation to check security type in API implementation before calling into driver.

Adding another security type could potentially break our existing test case. An email is sent to the group to exercise the logic. A better approach, along with this change, is to update port specific WiFi implementation to check security type in API implementation before calling into driver.

Agree. All the port specific implementation should be updated to validate the arguments and return error to the caller if the port doesn't support eWiFiSecurityWPA2_ent

@sathishm6
While we are investigating what's the process to update all ports, could you elaborate why a new security type is needed?
I'm on an other thread with Mike, and I'm assuming this PR is related to what he's working on. From the code he shared with me, I do not see eWiFiSecurityWPA2_ent is used in your iot_wifi.c. (whd_tosecurity() and whd_fromsecurity() need to be updated in your iot_wifi.c at least, I did not check driver code.) If I'm understanding correctly, it is AP authenticates SSID/password/security type combination, not station. So a new security type does not have huge functional impact for what's coming, would that be a correct statement?

@sathishm6
While we are investigating what's the process to update all ports, could you elaborate why a new security type is needed?
I'm on an other thread with Mike, and I'm assuming this PR is related to what he's working on. From the code he shared with me, I do not see eWiFiSecurityWPA2_ent is used in your iot_wifi.c. (whd_tosecurity() and whd_fromsecurity() need to be updated in your iot_wifi.c at least, I did not check driver code.) If I'm understanding correctly, it is AP authenticates SSID/password/security type combination, not station. So a new security type does not have huge functional impact for what's coming, would that be a correct statement?

@yuhui-zheng  - eWiFiSecurityWPA2_ent security type is used for connecting the device to an enterprise security Wi-Fi network. This features is  going to be supported in Cypress platform as part of the upcoming AFR release we plan to make. With that release, the corresponding changes that are required to support enterprise security feature in iot_wifi.c will also show up. The primary reason for creating this PR is to overcome AmazonFreeRTOSSourceIntegrity failures we see in our Qual tests. In summary, without this change showing up on the AFR mainline, we can't pass AmazonFreeRTOSSourceIntegrity test. And if we don't pass AmazonFreeRTOSSourceIntegrity tests, we can't get through the Vendor Qual which will have all the relevant pieces of the software for enterprise security feature support.

@sathishm6  Given we have a pending release, I'm moving this PR to release-candidate branch to run with our infra. The hope is to get this enum into the coming release, thus to unblock the qualification. https://github.com/aws/amazon-freertos/pull/1630
As for API change or port change, I'm creating an internal issue to keep track of this.


Missing documentation

There is no documentation for the jsx-one-expression-per-line rule (#1497).
Also, the readme is missing a link to the documentation for the button-has-type rule (#1525).

Thanks for reporting this! I added the link to button-has-type rule.
@TSMMark since you wrote the code for the jsx-one-expression-per-line rule, would you be willing to add the documentation as well?

Sure thing. Anything I need to do other than the following?

add a file in docs/rules/
update readme with a link

That's it 👍

See #1552


Format code with google/yapf

Reformat code using google's yapf python formatter. There were some inconsistencies that this tool should fix. Next I would like to plug this into the travis build to either auto-format code on PRs or fail the build if the format isn't correct. This PR should be purely cosmetic and not affect functionality.

Thanks Charlie! Sounds good on adding to travis too, I will take a look at the flappers in separate


Step by Step Walkthrough out of date

The step by step walkthrough appears to reference deprecated code / modality of work.
The line: "Open the "estimate-drift" script and click run. The user interface opens." in the readme should probably be correct to use the current script names & perhaps and indication of where/how to find them in the menu.

Updates are now done with the new release. Any new comments or corrections are very welcome. Cheers!


fix FluentNavMenu.razor.js for Blazor Hybrid/MAUI

Pull Request
📖 Description
Prevents listeners from being added when running in BlazorWebView
🎫 Issues
Event listeners are being added to collapse/expand button for FluentNavMenu when used in Blazor Hybrid/MAUI.
👩💻 Reviewer Notes
This is an addtional fix related to #1560 that did not cover Blazor Hybrid/MAUI.
The fix is based on determining if the component is running in BlazorWebView.
function isRunningInWebView() {
    return navigator.userAgentData.brands.find(e => e.brand == 'Microsoft Edge WebView2') != null;
}

📑 Test Plan
I ran all the tests that I used for #1560. I created a new Blazor Hybrid/MAUI application created from the default template and updated it with the Fluent components to match the defaults created for a server rendered webassembly application to verify the desired behaviour.
✅ Checklist
General

[ ] I have added tests for my changes.
[X] I have tested my changes.
[ ] I have updated the project documentation to reflect my changes.
[X] I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

[ ] I have added a new component
[ ] I have added Unit Tests for my new compontent
[X] I have modified an existing component
[ ] I have validate Unit Tests for an existing component

⏭ Next Steps

@dvoituron
I was debating submitting this PR but decided to draft one so the behaviour would consistent across the different hosting/rendering options. I agree that this definitely 'smells'.
I've also discovered additional quirks related UI state not being preserved when transitioning from static rendered to Blazor rendered.

If you collapse the menu as soon as the UI appears, it will suddenly expand when Blazor rendering/interactivity is available.
There's actually an additional transition when the interactivity option is WebAssembly. Once for the server static rendering, again when WebAssembly starts the page, and finally when completely running in WebAssembly.

This also violates this note in the documentation regarding not coupling to render mode.
All of this to provide the collapsing and expanding functionality of the FluentNavMenu when statically rendered.
As for the source of problem, I'm still trying to figure that out. :smile:. I've learned a lot about the rendering process as I've looked at this issue. I've been unable to find any detailed documentation on the transition from static rendered to interactive rendered.
I've also considered but not tried:

Removing the event listener added in JavaScript in the OnInitializedAsync. This is likely going to exhibit the quirky behaviour I mentioned above as well.
Moving the desired behvaiour into Javascript only so that the collapse and expand behaviour is only handled in JavaScript. This would be my next candidate to explore more thoroughly.

I've been doing some further research looking for a root cause as per Denis's comments.
I found https://github.com/microsoft/fluentui-blazor/blob/3f9a21f4f26e37a400a30ad462efb89a5e7960ac/src/Core/Components/NavMenu/FluentNavGroup.razor#L39
Data is a property inherited from Microsoft.FluentUI.AspNetCore.Components.FluentComponentBase. It is being used to prevent the script from being run https://github.com/microsoft/fluentui-blazor/blob/3f9a21f4f26e37a400a30ad462efb89a5e7960ac/src/Core/Components/NavMenu/FluentNavMenu.razor#L3-L6
An alternative to making any code changes to the FluentUI-Blazor library would be to explicity do this in the NavMenu component on a per application basis for Blazor Hybrid/MAUI and WebAssembly hosted applications.
@dvoituron @vnbaaij Thoughts??
Note: This still does not address the UI state transition issues. See https://github.com/microsoft/fluentui-blazor/pull/1633#issuecomment-1979332854

I'm using the Data parameter to prevent the script from being included multiple times when the menu hase a couple of layers. It does not prevent the script form being run.

I'm using the Data parameter to prevent the script from being included multiple times when the menu hase a couple of layers. It does not prevent the script form being run.

That makes sense. I forgot to include the following screenshot above😞.

I made this change to the NavMenu component in the Blazor Hybrid/MAUI and WebAssembly hosted test applications and it effectively gave me the results I wanted. The javascript listeners were not added. Both these applications defaulted to using the Blazor provided event handler.
It's basically a temporary work-around for 4.4.1. I'm currently using it in my production WebAssembly hosted application where I originally ran across this issue. 😄
I'm still looking into a better long term fix that would also address UI state change issue.

An alternative to making any code changes to the FluentUI-Blazor library would be to explicity do this in the NavMenu component on a per application basis for Blazor Hybrid/MAUI and WebAssembly hosted applications.

Indeed, I prefer to have an explicit property (for example by adding an option to AddFluentUIComponents) and if it's possible to define a default value using the detected environment (MAUI, Web, ...).

An alternative to making any code changes to the FluentUI-Blazor library would be to explicity do this in the NavMenu component on a per application basis for Blazor Hybrid/MAUI and WebAssembly hosted applications.

Indeed, I prefer to have an explicit property (for example by adding an option to AddFluentUIComponents) and if it's possible to define a default value using the detected environment (MAUI, Web, ...).

@dvoituron I think the explicit declaration is the way to go.
As I reflect on how this started and on @vnbaaij comment, Enhanced navigation should not have applied. I think this is a Blazor bug.
When a Blazor Web App is first pre-rendered/statically rendered, the javascript for static SSR is sent to the browser where it's executed on the enhancedload event. When the application is ready, another render occurs but this time there is no enhancedload event.
In Blazor Hybrid/MAUI and WebAssembly hosted applications, no pre-rerendering is done but the enhancedload event is still being triggered on first render. Preventing the enhancedload event from occuring would make the component behaviour consistent no matter the hosting environment.
If this is truly a bug, by explicitly declaring it would make it easier to deprecate in the future when it's fixed.
Assuming that using an explicit property as the approach, how should it be implemented?
I see two options:

Add an option called 'UseStaticSsr' with a default value of true for AddFluentUIComponents. UseStaticSsr would need to be explicitly set to false for Blazor Hybrid/MAUI and WebAssembly hosted applications. Add logic that conditionally checks for this option before including fluent-page-script in the FluentPageScript.razor file.
Add a property to FluentNavMenu named UseStaticSsr with a default value of true. Then conditionally check this in FluentNavMenu.razor.

Note:

Currently only the FluentNavMenu component is using the FluentPageScript component that adds the javascript for static SSR. Adding an option to AddFluentUIComponents could be considered overkill.
As for detecting the environment, the only method I've found so far is in javascript so far.

I can see pros and cons for either option. Thoughts?

@dvoituron I think the explicit declaration is the way to go.
As I reflect on how this started and on @vnbaaij comment, Enhanced navigation should not have applied. I think this is a Blazor bug.
When a Blazor Web App is first pre-rendered/statically rendered, the javascript for static SSR is sent to the browser where it's executed on the enhancedload event. When the application is ready, another render occurs but this time there is no enhancedload event.
In Blazor Hybrid/MAUI and WebAssembly hosted applications, no pre-rerendering is done but the enhancedload event is still being triggered on first render. Preventing the enhancedload event from occuring would make the component behaviour consistent no matter the hosting environment.

Yes, that is the ultimate goal.

If this is truly a bug, by explicitly declaring it would make it easier to deprecate in the future when it's fixed.
Assuming that using an explicit property as the approach, how should it be implemented?
I see two options:

Add an option called 'UseStaticSsr' with a default value of true for AddFluentUIComponents. UseStaticSsr would need to be explicitly set to false for Blazor Hybrid/MAUI and WebAssembly hosted applications. Add logic that conditionally checks for this option before including fluent-page-script in the FluentPageScript.razor file.

I think this is the way to go.

Add a property to FluentNavMenu named UseStaticSsr with a default value of true. Then conditionally check this in FluentNavMenu.razor.

This seems like a too specific solution for me.

Note:

Currently only the FluentNavMenu component is using the FluentPageScript component that adds the javascript for static SSR. Adding an option to AddFluentUIComponents could be considered overkill.

The NavMenu is the only place I've added it on purpose. I anticipate that we would like to have more components that offer enhanced functionality (other than just displaying) when used in a SSR scenario. Because of the issues this is giving, I have not yet looked at which components we could use this. If we do, I expect we will be using the FluentPageScript again.

As for detecting the environment, the only method I've found so far is in javascript so far.

I believe extra/new/better functionality is on the roadmap. I'll sk the Blazor team what is the est way to do this now.

Background
I thought the root cause of the issue was that the enhancedload event was the cause of this issue so I filed an issue. After some feedback from @MackinnonBuck and attempting to create a minimal repro, I discovered a difference between how PageScript and FluentPageScript was implemented. The latter was a pretty faithful implementation in Typescript. The primary difference is was when the handler was added to the enhancedload event.
In PageScript we have in BlazorPageScript.lib.module.js:
export function afterWebStarted(blazor) {
    customElements.define('page-script', class extends HTMLElement {
        static observedAttributes = ['src'];

        // We use attributeChangedCallback instead of connectedCallback
        // because a page-script element might get reused between enhanced
        // navigations.
        attributeChangedCallback(name, oldValue, newValue) {
            if (name !== 'src') {
                return;
            }

            this.src = newValue;
            unregisterPageScriptElement(oldValue);
            registerPageScriptElement(newValue);
        }

        disconnectedCallback() {
            unregisterPageScriptElement(this.src);
        }
    });

    blazor.addEventListener('enhancedload', onEnhancedLoad);
}

In FluentPageScript, this initialization is done in the index.ts file.
https://github.com/microsoft/fluentui-blazor/blob/072a9388e9bdb6dfe83573e14c45a786c13f04ad/src/Core.Assets/src/index.ts#L297-L299
and
https://github.com/microsoft/fluentui-blazor/blob/072a9388e9bdb6dfe83573e14c45a786c13f04ad/src/Core.Assets/src/index.ts#L304-L310
Why is happening?
customElement fluent-page-script is always defined in index.ts. This means that attributeChangedCallback in FluentPageScript.ts is called in for any fluent-page-script tag present.  This in turns calls registerPageScriptElement that calls initializePageScriptModule which then calls the onLoad in FluentNavMenu.razor.js.
onLoad is triggered by attributeChangedCallback NOT by the enhancedload event. And because the customElement fluent-page-script is always defined. The Javascript handlers were always added to the toggle.
Fix
The fix is to move line 307 to after line  297.

This fix also addresses the root cause of #1560 as well.

@vnbaaij

The NavMenu is the only place I've added it on purpose. I anticipate that we would like to have more components that offer enhanced functionality (other than just displaying) when used in a SSR scenario. Because of the issues this is giving, I have not yet looked at which components we could use this. If we do, I expect we will be using the FluentPageScript again.

Thanks Gary for perservering in finding the root cause!


Commitlint is failing in CI

For, like, no reason.
Not sure what's up. Too tired to look now.

Ref wagoid/commitlint-github-action#340


equihash integration

@khovratovich
Not, sure if I can phrase my query right. I'm not that technical into C ++, just wondering how can we implement and integrate equihash algo into our mining application? Any hint, guide or reference will be appreciated to achieve this.

Based on pow.cc:
//Create PoW challenge
Equihash equihash(n,k,seed);

//Solve it
Proof p = equihash.FindProof();

//Verify the solution
bool valid = p.Test();

So you'd want to download the challenge info from the mining pool, solve it, and send the solution back to the pool for it to verify it.

How difficult would it be to have the yiimp fork support this algorithm? It seems to be based off both blake2 and blake2b which if i remember correctly the yiimp based mining application supports as well.


Compiling a subresource with an extension validates the subresource against the root extension schema.

I'm attempting to parse OpenAPI 3.1 specifications and I can validate the root of the document without issue, but I'm trying to process individual JSON schemas within the spec independently and I'm running into trouble.
This is a loose copy of what I'm trying to do:
comp := jsonschema.NewCompiler()

if err := comp.AddResource("https://spec.openapis.org/oas/3.1/schema/2022-10-07", oas31Reader); err != nil {
	return nil, err
}

oas31Schema, err := comp.Compile("https://spec.openapis.org/oas/3.1/schema/2022-10-07")
if err != nil {
	return nil, err
}

comp.RegisterExtension("openapi_3.1", oas31Schema, &oas3SchemaCompiler{})

if err := comp.AddResource("my-openapi-spec", in); err != nil {
	return nil, err
}

fullSpec, err := jsonschemaCompiler.Compile("my-openapi-spec")
if err != nil {
	return nil, err
}

// everything fine so far

subSchema, err := jsonschemaCompiler.Compile(fmt.Sprintf("%s#/components/schemas/Foo", "my-openapi-spec"))
if err != nil {
        // bang! this breaks here
	return nil, err
}

I get the message that #/components/schemas/Foo does not have required properties "openapi" and "info".
It appears that in Compiler.validateSchema()  we range over all the extensions on the compiler and validate that the current doc is valid according to that extension. This is fine, except I need it to validate based on the current vloc, and not on the root of the extension schema.
I'm still trying to get to grips with how the library is implemented, but it could also be an issue in Schema.validate(), since it doesn't seem to take vloc into account.
Or, I could just be doing something wrong, any help would be appreciated!

If you can share the complete source code, and some example of what your extension is trying to do, then it would help me understand your issue.

I've created a fork and committed an example you can run with go test, see openapi_test.go:
https://github.com/dan-j/santhosh-tekuri-jsonschema/tree/142-extension-subschema-validation

Updated with some comments ^

I had a look at your source code; it seems you got confused "what is meant by extension"
openapi document is a json document. and its jsonschema is openapi_3.1.schema.json (note that you are confused that openapi_3.1.schema.json is the schema of extension. no it is not)
openapi uses jsonschema to specify schema for request and responses. but in addition to standard jsonschema it includes few additional keywords discriminator, xml, externalDocs and example (see Fixed Fields section in https://spec.openapis.org/oas/v3.1.0#schema-object)
among the above 4 keywords, only discriminator effects validation. rest of them are just for documentation purpose
so you have to write an extension for discriminator keyword. and the schema for this is at  https://spec.openapis.org/oas/3.1/meta/base

now if you want to understand why you are getting validation error in your specific implementation:
you created an extension whose schema is openapi_3.1.schema.json. and openapi_3.1.schema.json says, openapi and info are required.  So when you use this extension you are saying: I am introducing two new keywords openapi and info which are mandatory. So you are getting validation errors in schema compilation.

Ahh ok. So I was under the impression that extensions would only be applied if the ExtCompiler returned an ExtSchema, which for the full spec, it contains "openapi" so I return a noop schema, but for others I am returning nil.
I'm going to close this, thanks for your response!

extensions are always applied.
that mean your schema must be valid against all the registered extensions.
the extension.validate implement should look for its keywords and do the validation logic


Cant copy to anywhere bar its current folder.

I am trying to copy a document from one folder to another inside my document library. I am able to copy the file into the same folder but not outside of it. I have tried using the parentRefernce object. Using  an ID a path trying to copy it to the root of the drive as well as the folder I actually want to put it in but keep getting the same error.
Id = 137, Status = RanToCompletion, Method = "{null}", Result = "error": "code": invalidRequest message: The request is malformed or incorrect.
"innerError":   request-id: 10989d70-c07b-4ce3-87de-ceec8f481691

Hi @kking1991, can you give us an example request body so we can see what you're sending us?

{"ParentReference":{"DriveID":  "this is my document library drive id ",
"ID":" this is the id of the folder i want to move it to.",},
"Name":"copytemplatetoanotherfolder4.doc"}"
As documented on the api copy documentation however the format of my ids is not the same. My drive id is a lot longer than shown in the example. My id for the folder is not in the guid format either.
The request works when i take out the parent reference object. It creates the new copy inside the same folder. So i assume that the ids I'm using for the parent reference are incorrect but I have not been able to find an alternative id value.
Thanks

Been resolved need to add jsonProperty annotation to my parent reference object. thanks anyway.

Thanks for updating us!


initial brazilian commit

@nanexcool Hola Hermano!
Initial commit for brazilian portuguese! Its hard to translate some terms, we still use a lot of english terms like "burn rate" hehe.

All good! There's some terms in Spanish that we also often don't translate ;)
Thank you!


update role-based-access-control-rbac.md

fixed the link

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Dear @JohanFreelancer9 , thank you very much, your recommendation was applied.
Thank you

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin Changes look correct. Could you please review and merge? Thanks!


[WFLY-17955]: Upgrade to Smallrye opentelemetry 2.3.2.

Upgrading smallrye opentelemtry to 2.3.2 to fix JAXRS integration.

Jira: https://issues.redhat.com/browse/WFLY-17955

Thanks @ehsavoie, @jamezp and @jasondlee


Update broken Twitter links and Improve README.md

Currently, the Twitter links are broken. Consider replacing them with actual profile links or remove them completely.
Improve grammatical structure of README and fix typos

@slim-codes which twitter links are you talking about


@orta: Reader Updates

Removes some dead code, removes reference cycles, and terminates signal when the VC disappears (cancelling or using a test CC token would make the signal persist, forever).

looks good, ships

CI will likely fail on this, but I've tested locally fine. We're tracking CI problems on Trello.


Make code regions error before recording itself in dependency graph (when possible)

Right now, if a Banyan job fails, it gets completely shut down. But unfortunately the user can't always just restart the job because data might be partially written. Now for errors because of large data, node failures, or split/merge/cast functions; this is a big issue where we need to have better resilience and some sort of retry logic with atomic writes; also, reusing failed jobs as warmed up jobs would be nice.
But for runtime error because of incorrect usage of an API, we should be able to catch these before we even send annotated code regions to the Banyan backend for scheduling. We just have to modify the @partitioned macro to first include the original code (which is run on cached data samples) with $(esc(code)) before actually submitting a task to be scheduled with record_request(RecordTaskRequest(task)) and finish_task().
This would allow us to catch a considerable amount of runtime error without actually crashing a job created with create_job. This would be useful only for REPL/notebook users because for other cases, you would probably run create_job

Resolved


add a simple github CI action to test build on PRs and pushes

this CI script will run as a github action on every git push and PR to this repo.
it simply runs an ubuntu image, installs dependencies, then executes cargo run.
sample output

Since we use a lot of nightly features, and warnings may indicate things we can change. Is there a way to make this CI pipeline make warnings as errors. However, I don't want it to globally make warnings as errors due to that hurting intra-day development processes.

Is there a way to make this CI pipeline make warnings as errors?

Implemented here: #16.


Build pipeline

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: irenor sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


merge: dev to master

:tada: This PR is included in version 0.122.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added pdf merger

added a python project
closes #250
Demonstration -
https://user-images.githubusercontent.com/91176055/161818878-cef6d4d8-c1a6-421c-82ed-efbc20f1795b.mp4

Please review @pranjay-poddar

Add screenshots

Add screenshots

Added a working video


Extension causes high cpu load

Issue Type: Performance
Extension Name: bracket-pair-colorizer-2
Extension Version: 0.0.28
OS Version: Darwin x64 18.2.0
VSCode version: 1.31.1

:warning: Make sure to attach this file from your home-directory: /Users/onyx/CoenraadS.bracket-pair-colorizer-2-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #55. Please close this and post there instead.
@Bhaskar116


SSO Credential Support - does not recognize SSO Tokens in AWS Credentials file

Description
We are using AWS CLI SSO Tokens in our aws .credentials file but they are not recognized as a supported way of authenticating to AWS and an exception message is shown to reflect this. I believe this is because this package is quite far behind the current AWSSDK.Core package version
Reproduction Steps
Try to use an CLI SSO Token in credentials file and an exception is thrown indicating that SSO is not supported.
Environment
version 2.1.0
Resolution
Update this package to use the latest awssdk.core package (via updating AWSSDK.Extensions.NETCore.Setup to the latest version)

This is a :bug: bug-report

Hi @listylister,
Good afternoon.
Thanks for posting the issue. Could you please elaborate on how you are planning to use SSO tokens with Systems Manager in ASP.NET Core application? Based on similar issues, user has to execute aws sso login from AWS CLI before using these credentials via AWS .NET SDK.
Thanks,
Ashish

Hi, it's for local development purposes only. So we don't have to
copy/paste and auth tokens into the credentials file we plan to use as
tokens to authenticate our local development environment instead.
Hope that makes sense.
Thanks
On Fri, 2 Jul 2021, 9:09 pm Ashish Dhingra, @.***>
wrote:

Hi @listylister https://github.com/listylister,
Good afternoon.
Thanks for posting the issue. Could you please elaborate on how you are
planning to use SSO tokens with Systems Manager in ASP.NET Core
application? Based on similar issues, user has to execute aws sso login
from AWS CLI before using these credentials via AWS .NET SDK.
Thanks,
Ashish
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-dotnet-extensions-configuration/issues/95#issuecomment-873233230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA27H5SKY6TZW7OTJ3HBG33TVYMF7ANCNFSM47WCXDFQ
.

I seem to be having a similar problem, when I do an aws sso login --profile profieName then I configure appsettings.json's profile to profileName nothing is loaded with exceptions being thrown around AWSSDK.SSO and AWSSDK.SSOOIDC missing.
Once I add those packages, the extension works as expected.

Afraid I get the same error, even after adding those packages...here is a screenshot - it just doesn't like the fact that default is an SSO profile.

Yeah, one of my employees tried to use the project on his machine and was getting the same errors about missing types even though he had the packages I mentioned installed, then he updated the packages from <IP_ADDRESS> to <IP_ADDRESS> and then he was able to see values in the SecretsManager configuration section. Before that he would have a 1 minute timeout while the AWS API call blocked trying to load the configuration before the API would turn on.

Amazon.Extensions.Configuration.SystemsManager 2.1.1 released with the support for SSO credentials.