Fuzzing: Add parse k8s object fuzzer

Adds a fuzzer for object.ParseK8sObjectsFromYAMLManifest
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @AdamKorcz. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

/ok-to-test

@AdamKorcz: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

integ-pilot-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

integ-security-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-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

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

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

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

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

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

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

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

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

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

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

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

integ-security-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

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

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

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

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

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

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test analyze-tests_istio

integ-operator-controller-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-operator-controller-tests_istio

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

lint_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test lint_istio

release-test_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-cni-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-cni-k8s-tests_istio

integ-multicluster-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test unit-tests_istio

release-notes_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test release-notes_istio

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

integ-helm-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-pilot-multicluster-tests_istio

integ-distroless-k8s-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-distroless-k8s-tests_istio

integ-security-multicluster-tests_istio
a19b781eeac04fc4c6399a9dca24db4c0f9a244a
link
/test integ-security-multicluster-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.

@AdamKorcz: 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.

@AdamKorcz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
2128ab52dc3dd9314ccf5d08f9f041ddb9820b70
link
/test integ-pilot-multicluster-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.

The failed test looks like a flaky to me. I will wait a bit with retesting.

Yeah there was a bad PR merged, revert should land soon

/retest

@AdamKorcz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
2128ab52dc3dd9314ccf5d08f9f041ddb9820b70
link
/test integ-pilot-multicluster-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.

@AdamKorcz: 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.

@AdamKorcz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
2128ab52dc3dd9314ccf5d08f9f041ddb9820b70
link
/test integ-pilot-multicluster-tests_istio

integ-istiodremote-k8s-tests_istio
2128ab52dc3dd9314ccf5d08f9f041ddb9820b70
link
/test integ-istiodremote-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.


Feat: Editable billable flag

Details

This PR is to view and edit a billable toggle on an already created money request.
To create a money request please insert this to App.js with your policyID you are testing:
    window.Onyx.merge(`policy_${YOUR_ID}`, {
        disabledFields: {
            defaultBillable: false,
            reimbursable: false,
        },
        defaultBillable: false,
    });

And you need beta - newDotTags
Fixed Issues

$ https://github.com/Expensify/App/issues/26793
PROPOSAL: https://github.com/Expensify/App/issues/26793#issuecomment-1726077842
Tests

Login to the app
Create a new money request.
Dive into the created requests to edit .
Verify that there is a Billable toggle.
Try to change toggler
After we refresh page, selected toggle should remain.
After we close edit mode and go again, selected toggle should remain.

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

None

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[x] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Reviewer Checklist

[X] I have verified the author checklist is complete (all boxes are checked off).
[X] I verified the correct issue is linked in the ### Fixed Issues section above
[X] I verified testing steps are clear and they cover the changes made in this PR

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[X] I checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[X] I verified tests pass on all platforms & I tested again on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[X] I verified proper code patterns were followed (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I verified that this PR follows the guidelines as stated in the Review Guidelines
[X] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@amyevans Updated all your comments!

Posted in our Slack thread as well, but am not seeing the appropriate system message when testing (offline for now, since backend changes are still pending). Could you take a look?

@amyevans
Updated once again:

Ah I see where the disconnect is. The system message should appear on the transaction thread, not the expense report
https://github.com/Expensify/App/assets/7277067/5428e776-19c6-4277-b0db-3013fb055657

@amyevans Ahhh, get it, sorry for this disconnection..
Will change it tomorrow

Thanks!

@amyevans Finally found that I was sending wrong reportID, from transaction, but not from report itself, thats why message was appearing in the expense report, now it works fine

@amyevans Done!

🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.75-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@amyevans @robertKozik  is this still behind beta?

@kavimuru yes it's behind beta!

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.76-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


update "latest draft" and add self to contributor

as discussed on today's call

oops @OR13 you were too quick, make sure I didn't do anything too dumb on this one last commit that I hadn't made when you reviewed (the others are just committed your inlines)

While review from everyone in the group is warmly welcome, I would be remiss if I merged this without giving @brentzundel 2 weeks to review this!


Add TypeScript definition for exported functions

Seems to work, and is useful for TypeScript folks.

Please rather submit TypeScript definitions to https://github.com/DefinitelyTyped/DefinitelyTyped.


chore: fix link typo in name system spec, rename name system binary

Some cleanups from bootstrap script. Renaming the binary utility to nns, as "bootstrap" is what we specifically do to enable discovery in a noosphere name system network, and allows additional methods (e.g. "query") that operate on a noosphere name system, unrelated to the act of "bootstrapping".

I'm totally fine with nns (and I think it's probably the most appropriate name for this) but I want to call out for posterity that I heard @blaine use this name for Fission's aspirational name system before we landed this, so they should get dibs on it if they want it :sweat_smile:

Thanks @cdata! My current plan is to call the protocol NNS, and since a single executable should be all that's needed to join/run/do lookups against the service, nns feels like an appropriate executable name for it, if it's not too much trouble to avoid a conflict for now? I've made some progress on the design, writeup soon. This week, though... what even is this week. 🙃
(haven't had a chance to review your code here again, just playing catch-up, but I could imagine this actually being the basis for the nns service in any event! I have no precious notions of us writing code from scratch vs contributing to your start here)

Thanks @cdata! My current plan is to call the protocol NNS, and since a single executable should be all that's needed to join/run/do lookups against the service, nns feels like an appropriate executable name for it, if it's not too much trouble to avoid a conflict for now? I've made some progress on the design, writeup soon. This week, though... what even is this week. upside_down_face
(haven't had a chance to review your code here again, just playing catch-up, but I could imagine this actually being the basis for the nns service in any event! I have no precious notions of us writing code from scratch vs contributing to your start here)

Renaming this currently internal tool to avoid conflicts is no problem -- pushing changes to rename this to orb-ns for lack of bikeshedding and using orb from the primary noosphere CLI.
@blaine the latest NS docs are here, would appreciate any insight and feedback for sure, and would love to scope out your writeup on the protocol NNS when it's ready! The internal implementation of our NS (noosphere-ns) has an agnostic DHT layer (noosphere_ns::dht), used by this little bootstrapper utility as well, that could be expanded to support something like "Protocol NNS" in either a generic or "standardized" sense (e.g. some UCAN/key patterns) -- happy to jam on some common ground and reusability here!


Return parameter seen as non existing statement

Error by linter: "Statement does not exist in ABAPv740sp08(or a parser error), "rv_inbound_fm" "
(code has been ok seen by the linter earlier)
For the following method definition/implementation.
`    METHODS get_inbound_conversion_fm
IMPORTING
!iv_table            TYPE tabname
!iv_field            TYPE fieldname
RETURNING
VALUE(rv_inbound_fm) TYPE rs38l_fnam
RAISING
zcx_exception .
METHOD get_inbound_conversion_fm.
rv_inbound_fm = 'CONVERSION_EXIT_' && get_field_ref( iv_table = iv_table
                                                     iv_field = iv_field )->edit_mask+2 && '_INPUT'.

ENDMETHOD.`

@DennisLybecker-INVIXO thanks
try again, 2.58.19 published

Perfect, thanks, works again.


mysql: select * from mysql.user crashes the query panel

Any updates on this issue? I'm using version 4.1.0 and it's still crashing.


NIFI-5378 prevent duplicate keys with different values in nifi.p…

…roperties

Summary
When loading nifi.properties file, first check for duplicate key/value entries. Duplicate keys are allowed if their values are the same. If the same key has different values, an error with key/value details is written to nifi-app.log and NiFi will not start.
NIFI-4278
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Installed NiFi and attempted to start with various combinations of key/value duplicates.
Duplicate keys with unique values
Duplicate keys with same values
All unique keys
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 8
[X] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

I'm a little bit hesitant on this. I think adding a WARN log message makes sense. But if I'm reading this correctly, this would prevent NiFi from starting in the case of duplicate properties? Do we have a reason that we need to do this?
With .properties files, if there are duplicates, the last entry in the file wins. And because of this it's pretty common to see scripts such as:
echo "nifi.my.property.value=My-Value" >> nifi.properties
echo "nifi.your.property.value=Your-Value" >> nifi.properties

In doing this, we append the line to the end of nifi.properties, and this can be done to set the properties as we want. The alternative would be to use sed or something like that, but that can be more complicated.
To be clear here, I'm not saying that I'm a -1 and I think we should avoid this. But we should be careful here and realize that introducing this could break some people, so we need to make sure that introducing this new restriction provide a benefit that is helpful enough to outweigh the potential downside.

@markap14 It seems to me it is a high risk to allow NiFi to start with duplicate properties (with different values.) You've presented one use case where users simply append updated properties at the end of the file. This approach is susceptible to unnoticed configuration errors. Different values represent an ambiguous configuration. A user not in the know will not even be certain if the last property takes precedence or the first - or is it random? The documentation makes no mention of this. Therefore, we are in the gray area requiring the user to assume - never a good position to be in.
That is largely the point of this ticket: to ensure a well-defined, unambiguous state of the application. I don't find that prospect overly limiting nor ill advised.
The use case which brought about this ticket is a user (or maybe it was an automated script.. it's been lost to history a bit) updated nifi.properties in a similar way as you mentioned. However, operators looked at nifi.properties, and specifically looked at the area of the file that is commented and documented to hold certain properties, e.g. "# security properties #". Those values were correct, but a new property was added towards the end of the file and was unnoticed.
So, we seem to be discussing the valid - or advisable - structure of the nifi.properties file, and the appropriate response of the application. Through this ticket, I would argue that it is not recommended to allow the properties file such wide latitude of property loading. There is very little downside to being more strict, yet potentially costly results for being more lax. I think it is perfectly reasonable to disallow start with the reason being logged. (In fact, failure happens so quickly that the log file is extremely short making it immediately obvious what the problem was.)

@NissimShiman I think I would avoid added yet another property, just to control how we load properties. When adding properties, there's generally a balance, where adding more properties = more flexibility but more complexity. Fewer properties = less flexible but simpler.
@markobean "Through this ticket, I would argue that it is not recommended to allow the properties file such wide latitude of property loading. There is very little downside to being more strict, yet potentially costly results for being more lax."
I think there are arguments to be made for each side.
Personally, I don't really have a strong preference one way or the other. Just wanted to make sure that these things were being thought through.

@exceptionfactory I get your point about how properties are loaded with the increased flexibility naturally built into the Properties class. The problem with Properties.load() is it automatically turns the property keys into a Set which makes it impossible to find duplicates. The only way I thought of to do this was standard FileReader and going line by line. As far as I know, multi-line properties are not supported (and a test case putting a property in a new line verified that behavior.)
I'm not sure the characterset issues you mention are necessarily relevant in the check for duplicates. As long as the property values are being read the same way regardless of UTF-8, ISO-8859-1, etc. then the String compare would still be accurate for match/not match. Please correct me if you still think this is an issue.
Note that the duplicate check is performed separately from reading/storing actual property values. It is literally and solely a key/value pair per line sanity check.

@markap14 Its true that additional properties values add complexity ... Just putting out ideas to try to see what could work

@NissimShiman I think I would avoid added yet another property, just to control how we load properties. When adding properties, there's generally a balance, where adding more properties = more flexibility but more complexity. Fewer properties = less flexible but simpler.
@markobean "Through this ticket, I would argue that it is not recommended to allow the properties file such wide latitude of property loading. There is very little downside to being more strict, yet potentially costly results for being more lax." I think there are arguments to be made for each side. Personally, I don't really have a strong preference one way or the other. Just wanted to make sure that these things were being thought through.

@markap14 I get it. I do in fact see both sides. I believe it makes NiFi a stronger, more reliable application to follow best practices of failing safely.

@exceptionfactory The PR indicates you still have on outstanding requested change. The referenced comments discusses both IllegalArgumentException and overriding the put() method for a custom Properties class that will handles the duplicates like we want. I have addressed the latter.
Are you still anticipating a change to the exception? The exception will in fact prevent NiFi from starting, but that is as intended. The discussion with @markap14 describes the rationale in more detail.

@exceptionfactory The PR indicates you still have on outstanding requested change. The referenced comments discusses both IllegalArgumentException and overriding the put() method for a custom Properties class that will handles the duplicates like we want. I have addressed the latter.
Are you still anticipating a change to the exception? The exception will in fact prevent NiFi from starting, but that is as intended. The discussion with @markap14 describes the rationale in more detail.

Thanks for making the updates @markobean, the requested change status remains as I have not yet had chance to review the updates. I will take a closer look soon, but the recent changes look good from a cursory review.

@exceptionfactory The PR indicates you still have on outstanding requested change. The referenced comments discusses both IllegalArgumentException and overriding the put() method for a custom Properties class that will handles the duplicates like we want. I have addressed the latter.
Are you still anticipating a change to the exception? The exception will in fact prevent NiFi from starting, but that is as intended. The discussion with @markap14 describes the rationale in more detail.

Thanks for making the updates @markobean, the requested change status remains as I have not yet had chance to review the updates. I will take a closer look soon, but the recent changes look good from a cursory review.

Roger that. I just wanted to be sure I knew who's court the ball was in


MAAS-2979 | Add check_id to extras to log that plugin was not found

Coverage remained the same at 90.956% when pulling dd2a3729fbc4744861b2a0d32a8aac000bd1b34d on MAAS-2979-info-about-data-series-in-alert into d258dc9a365b32ee58dfa4b05b3ac5116304b895 on develop.