[NO MERGE] just to trigger test

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-build-test-e2e-pilot-no_auth

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-dashboard
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-dashboard

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-pilot-no_auth
2101a603c9921587c9bfe368e3ed7d2a569ed000
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-build-test-e2e-mixer-no_auth

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

Test name
Commit
Details
Rerun command

prow/release-build-test-upgrade-tests-1.1.7
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-istioctl-tests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-pilot-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-stackdriver
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-dashboard
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
b89cff40610bdad5591e7ff3fcee130e8b0c2581
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-dashboard
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-istioctl-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-dashboard
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-mixer-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-mixer-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-mixer-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-stackdriver
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-pilot-no_auth
b75a59f5ba391e61b169656873d186a955a5d580
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-pilot-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-pilot-no_auth

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.

@icygalz fyi Tide is stuck in "MERGE" on this: https://prow.istio.io/tide.
Not sure if that is a problem

/hold

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-pilot-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

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

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-pilot-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

prow/release-e2e-bookinfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-bookinfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istioctl-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-build-test-e2e-pilot-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-pilot-no_auth

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

prow/release-e2e-bookinfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-bookinfoTests

prow/release-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-bookInfoTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

prow/release-e2e-bookinfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-bookinfoTests

prow/release-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

prow/release-e2e-bookinfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-bookinfoTests

prow/release-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-simpleTests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-stackdriver
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-e2e-stackdriver

prow/release-e2e-simpleTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-simpleTests

prow/release-e2e-bookinfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-bookinfoTests

prow/release-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-e2e-pilot-no_auth

prow/release-build-test-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
9a9fca57f77d88e900b7ef613909d089f41f4826
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-mixer-no_auth
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-mixer-no_auth
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-bookInfoTests
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-pilot-no_auth
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-bookInfoTests
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-bookInfoTests
3c4e8ade66aa94054567f414713d51fdd1b4cf48
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-simpleTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-istio-unit-tests
53129eb93a9614e770b3d8ac183e6ef90b2ffc02
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-simpleTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-pilot-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-bookInfoTests
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istioctl-tests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-mixer-no_auth
6d16e76a8503f3b4084160f12831697f8d7b883c
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-bookInfoTests

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/release-build-test-e2e-simpleTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-simpleTests

prow/release-build-test-upgrade-tests-1.1.7
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-upgrade-tests-1.1.7

prow/release-build-test-istio-unit-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istio-unit-tests

prow/release-build-test-e2e-pilot-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-pilot-no_auth

prow/release-build-test-istioctl-tests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-istioctl-tests

prow/release-build-test-e2e-bookInfoTests
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-bookInfoTests

prow/release-build-test-e2e-mixer-no_auth
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-mixer-no_auth

prow/release-build-test-e2e-dashboard
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-dashboard

prow/release-build-test-e2e-stackdriver
b946217180174ed0ab8e91e9a5f5a35e6e592f8a
link
/test release-build-test-e2e-stackdriver

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.

closing this draft PR.. I will clean up the code changes and the open the real PR!! The tests are PASSING!!! WOOT WOOOOOT!!!!


Design idiomatic pattern for implementation and testing of Mutators

We should review the example mutators and identify good/bad practices.
Currently mutators are only done as integration tests.
We should probably look at this and see if its better done as an integration test.

So far I am thinking we can design the tests in a way similar to solidus_api's, which basically means providing GraphQL-specific 1) convenience methods for running the requests and 2) rspec matchers to test the responses.
In terms of making requests themselves, I'll provide two convenience methods:

One which uses a full POST or GET request and goes through the GraphQL controller. This will cause the requests to have the correct "context" attached to them when GraphQL executes. (Context is initialized in the controller and currently contains current_user and current_spree_store.)

One which uses Schema.execute() directly. This is a direct call avoiding any HTTP or controller action and its context is empty unless manually populated.

However, in practice there will be very little difference between the two methods -- the context which is initialized in the controller is the exact same context passed to Schema.execute(). So it is trivial to populate the context manually with current_store (or any other relevant values) and have the requests run as usual.
Comments/additional ideas welcome. Thanks!

Ok, further progress here.
First, I confirmed the assumption that in tests it only makes sense to have the expected GraphQL responses/results defined directly in/near the test rather than at the top of the file. Everything else is unusual/inconvenient.
Second, I also realized that (even though GraphQL supports it), it is impractical to keep the GraphQL queries listed in one string at the top of the file. There are two reasons for it:

In that case, the input/request and output/desired result are not self-contained in a test
Even more important, when queries are kept all in one string and chosen for execution with operationName parameter, then GraphQL still checks all queries against the GraphQL schema even if they won't be run. Which means that if any query is invalid, all tests fail because they all use the same big query.

So, with those considerations applied, I am pretty happy with how the generated code now looks:
# frozen_string_literal: true
require 'spec_helper'

module Spree::GraphQL
  describe 'Types::Shop' do
    #let!(:shop){ create(:store) }
    #let!(:context){ { current_store: shop } }
    #let!(:variables){ }

    # name: The shop’s name.
    # @return [Types::String!]
    describe 'name' do
      let!(:query) { { shop { name } } }
      let!(:result) { {"data":{"shop":{"name": shop.name}}} }
      #it 'succeeds' do
      #  execute query
      #  expect(response_hash).to eq(result_hash)
      #end
    end

    # description: A description of the shop.
    # @return [Types::String]
    describe 'description' do
      let!(:query) { { shop { description } } }
      let(:result){{"data":{"shop":{"description": shop.meta_description}}}}
      #it 'succeeds' do
      #  execute
      #  expect(response_json).to eq(result_json)
      #end
    end
  end
end

A couple things are important to note here:

The command to execute queries is just execute. It runs Schema.execute() with defaulting to query(), context() and variables() unless these params are manually provided.

The result which is expected to come from the query can be specified as either Ruby hash or JSON string. JSON is great if a person has the response JSON and just wants to match against it, and Hash is great if one wants to use variables in it and not deal with issues of variable interpolation and quoting within strings, etc.

After the query is executed, the result is saved to @response/response() as usual. Then there are additional helpers defined on it: response_json to get JSON string of the response, and response_hash to get Ruby hash of the response.

Finally, the same _json and _hash helpers are defined for result too. So to match the response with the expected result, one can use either one of these:

expect(response_json).to eq(result_json)

expect(response_hash).to eq(result_hash)

(The hashes are created with Rails' "indifferent access" to they support both strings and symbols as keys transparently.)
So, all in all pretty good.
The next things to work on from here are:

Improve the auto-generated code for mutations. I want the generator to generate basically fully valid mutation query and response templates, and this is a little bit more work than for basic queries because generator needs to support query inputs and response payloads.

In addition to execute which calls Schema.execute() directly, add post. Post would accept the same args but performs a HTTP POST and go through the controller. Whether to name it exactly post or choose a different/non-taken name

Comments/improvement requests welcome. Thanks!

(Still working on this one. I want the tests to be pre-generated with almost complete queries and expected results. Currently at some 45% of that effort.)

Coding of the generator is mostly done at this point. Doing final testing before updating the PR.


Macro support for cargo-free build systems

sqlx is great and being able to use the macros under a non-cargo build system brings it to more people. Bazel, buck2, and soong are just some examples of these build systems.
There are conceptually two places where cargo is run by sqlx: the prepare step and the build step.
This patch addresses the build step by optionally replacing the workspace lookup with an environment variable. For our case at least this is sufficient, as cargo can still be executed interactively, just not from with a build system action.
I'm happy to structure this differently (e.g. make the workspace lookup lazy) - just let me know.
Does your PR solve an issue?
Delete this text and add "fixes #(issue number)"

Closing in favor of #2927.


refactor: Updates the params of the identify function to match actual docs

https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-api

Now there is 1 more parameter: userHint (i.e. "friendly-name")

PLEASE MERGE THIS

Would be awesome to get this in!

You can actually use all the parameters of the official documentation. I made it generic so it can adapt to future adding of parameters. Here is an example :
identify('user-12345', {
'session': 'session-67890',
'page': 'page-abcdef',
'userHint': 'John Doe',
});


Add support for per-display settings

Closes #460, closes #615.
Related with: #608

@bbstats Thank you for your attention towards this feature. Due to the flexibility of the scheme design, I'm still not satisfied with the current user interface logic. Users may have difficulty distinguishing which scheme the merged settings originated from. However, I’ve decided to go ahead with the merge for now.


Added script for locust caller

looks good, you can merge it after addressing the dependecy comment

@AhmedMahdy14 looks good to me


Load model error in step3

When setting zero_stage=3, load my own ckpt in .pt format:
model = model_class.from_config(model_config)
print("")
print("model class", model_class)
for name, w in model.named_parameters():
print(name, w.shape)
print(model_config)
print("")
the shape of param is all torch.Size([0]);
With other zero_stages, the error will not occur.
I run the script line by line, the error does not occur either.
Anyone come across this problem?

The error message is:
size mismatch for model.decoder.layers.1.self_attn.k_proj.weight: copying a param with shape torch.Size([5120, 5120]) from checkpoint, the shape in current model is torch.Size([0]).
The ckpt I load is with correct shape of params, but the model build from config seems wrong.

Same error. The code of deepspeed chat in step3 , critic and reward model are all load with zero_stage=0 ,So i can't find example that how to load model from checkpoint with zero_stage=3.

mark

solved, have to load from pytorch_model.bin of pretrained huggingface model when using zero3, otherwise after setting HfDeepSpeedConfig (a must for zero3), model = model_class.from_config(model_config) will make all parameters of model zero tensors.

Actually we don't need to modify any codes in model_utils.py, which is used to load model. The best solution is to convert model format to .bin for all steps

@YingtongBu2 I used model.bin file in every step, but it doesn't work. I don't know where is wrong

@YingtongBu2 I used model.bin file in every step, but it doesn't work. I don't know where is wrong

do you solve the problem now?

Have you solved the problem?


Numba jit & Function Signature & Tuple int64

Function  "generate_trajectory_image" and  Tuple image_size as input type in function signature
@njit('Tuple((uint32[:,:],`` float32[:]))(float32[:,:], Tuple((uint64, uint64)))', parallel=True)
def generate_trajectory_image(points, `image_size):
...
def main(image_size=(1000, 1000), color_map='hot'):
img, extents = generate_trajectory_image(points, `image_size)
The function signature above with Tuple((uint64, uint64)) for image_size will work
However,
@njit('Tuple((uint32[:,:],`` float32[:]))(float32[:,:], Tuple((uint32, uint32)))', parallel=True)
will not work and throws the follwing error:
"AssertionError: Failed in nopython mode pipeline (step: native parfor lowering)
Storing i32 to ptr of i64 ('image_size_size0.19'). FE type int64"
This happens no matter if, where and which type (e.g. uint32) is declared for "image_size",
or also if no type definition is made for image_size
in the function signature only int64 or uint64 is accepted as type for the tuple.
Anything else throws an error as shown above
Full code see zip file or link

[ x] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html).
[ x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

python_bug.py.zip
code: https://gist.github.com/ratwolfzero/f3dc336019b583e5d7d69d689f57ed58

Seems the issue is related to the use of "parallel=True"
Without "parallel=True" Tuple((uint32, uint32)) is working
With "parallel"True" Tuple((uint32, uint32)) is not working

Thanks for the report. A couple of things for the future:

To get code to format in a text box that supports markdown, use triple back-ticks either side of the code block, example:```
<put your code here>
```

The Numba project does not accept reproducers that cannot be inspected as plain-text (with regards to the zip file above). Thanks for making the gist based version available too.

I've taken a look and extracted the part that is seemingly causing a problem and cannot seem to reproduce. Which OS, Python and Numba version are you using? An alternative to pursuing this route is to simply remove the signatures, Numba in general doesn't need them and often does better without them. Numba has a type inference engine that will work out the type of all the arguments and propagate these through to the return type. If you are interested in seeing what types Numba used, do something like my_jit_function.inspect_types() and they will be printed to your terminal. Hope this helps?


Health check time adjustment

Only change the timestamp on a health check when the status of the health check changes

After discussing with @dr-bonez, the timestamp is an a necessary component of the health check information that get stored in patch-db from a BE perspective. Data from patch-db is returned in the pure state it is stored as part of its API, so changing this functionality would change the overall behavior of patch-db.
As a result, @DrewAns it would be worthy to spend time time refactoring the FE logging behavior to account for frequent health checks / RPC responses in general.

Due to scaling performance concerns on the FE (subscriptions) as the service list grows, we will remove the timestamp from the record for now.


Update members.md

You are not on the official members list.  Also, this PR does not seem legitimate (odd casing, one-off account, links do not work)


[Bug] Timestamps should be cast for Redshift

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
There are downstream models in the dbt_greenhouse package that apply date transformations. If the user of the package is leveraging Redshift and the fields are synced as timestamptz then it will undoubtedly fail. We will want to cast the timestamp fields with {{ dbt_utils.type_timestamp() }} to avoid this error.
Relevant error log or model output
17:07:31    function pg_catalog.date_diff("unknown", timestamp with time zone, timestamp with time zone) does not exist
17:07:31    HINT:  No function matches the given name and argument types. You may need to add explicit type casts.

Expected behavior
The downstream models do not fail if the field is initially synced as timestamptz in Redshift
dbt Project configurations
N/A
Package versions
packages:

package: fivetran/greenhouse_source
version: [">=0.4.0", "<0.5.0"]

What database are you using dbt with?
redshift
dbt Version
v1.1.0
Additional Context

Initial dbt Slack thread where this issue was brought up
PR #18 that addresses this issue.

Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

The 0.4.1 release of the package includes the fix for this issue! 🎉


Error when evaluating SSR module /node_modules/sveltestrap/src/popper.js

I have a SvelteKit project and I recently started getting this error:
(node:36) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
2:19:03 PM [vite] Error when evaluating SSR module /node_modules/sveltestrap/src/popper.js:
/home/node/app/node_modules/@popperjs/core/dist/esm/popper.js:1
import { popperGenerator, detectOverflow } from "./createPopper.js";
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1027:15)
    at Module._compile (node:internal/modules/cjs/loader:1063:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
2:19:03 PM [vite] Error when evaluating SSR module /node_modules/sveltestrap/src/Dropdown.svelte:
/home/node/app/node_modules/@popperjs/core/dist/esm/popper.js:1
import { popperGenerator, detectOverflow } from "./createPopper.js";
^^^^^^

I thought Sveltestrap didn't include any external JS. As additional information, devDependencies includes "bootstrap": "^5.1.3", "sveltestrap": "^5.9.0", and "sass": "^1.49.9". Styles are imported in __layout.svelte with:
<style lang="scss" global>
  @import '../app.scss';
</style>

app.scss has the following line:
@import 'bootstrap/scss/bootstrap';

I'm not sure if this setup has anything to do with this error, but I thought more context is better than less. Thanks in advance for your assistance!

This seems to be an issue with Sveltestrap since this conflicts with the description of Sveltestrap:

This library was inspired by the reactstrap library for React. This does not depend on jQuery or Bootstrap's JavaScript, and instead uses Svelte.

Here's what I'm seeing in node_modules:
node_modules/sveltestrap/src/toggle.js
node_modules/sveltestrap/src/popper.js
node_modules/sveltestrap/src/index.js
node_modules/sveltestrap/src/DropdownContext.js
node_modules/sveltestrap/src/utils.js
node_modules/sveltestrap/src/transitions.js

While I can build my website without errors, I get the same error when I npm run dev then open my website. I do test against the latest LTS of node and svelte kit.
(node:10434) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
5:48:55 PM [vite] Error when evaluating SSR module /node_modules/sveltestrap/src/popper.js:
/Users/nates/dev/shy-svelte/node_modules/@popperjs/core/dist/esm/popper.js:1
import { popperGenerator, detectOverflow } from "./createPopper.js";
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1032:15)
    at Module._compile (node:internal/modules/cjs/loader:1067:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
5:48:55 PM [vite] Error when evaluating SSR module /node_modules/sveltestrap/src/Dropdown.svelte:
/Users/nates/dev/shy-svelte/node_modules/@popperjs/core/dist/esm/popper.js:1
import { popperGenerator, detectOverflow } from "./createPopper.js";
^^^^^^

System:
OS: macOS 12.3
CPU: (10) arm64 Apple M1 Pro
Memory: 1.21 GB / 32.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.14.2 - /opt/homebrew/bin/node
Yarn: 1.22.17 - /opt/homebrew/bin/yarn
npm: 8.5.5 - /opt/homebrew/bin/npm
Browsers:
Chrome: 99.0.4844.74
Firefox: 97.0
Safari: 15.4
npmPackages:
@sveltejs/adapter-node: next => 1.0.0-next.73
@sveltejs/kit: next => 1.0.0-next.301
bootstrap: ^5.1.3 => 5.1.3
svelte: ^3.46.4 => 3.46.4
sveltestrap: ^5.9.0 => 5.9.0

If I add:
  "type": "module",

to @popperjs/core/package.json, I can run without errors.

One suggestion... perhaps replace @popperjs/core with the latest version (now called @floating-ui/dom? The new library has type module in its package.json and the project has gone through a lot of cleanup.

same issue here!

For SvelteKit npm run build & preview all works OK, but errors are shown in dev: npm run dev
Cannot use import statement outside a module

And this error occurred to me once, but I can't get it back.
<Dropdown> is not a valid SSR component. You may need to review your
build config to ensure that dependencies are compiled,
rather than imported as pre-compiled modules

wouldn't #356 fix that issue?
@bestguy anyway this PR could be merged? :pray:

wouldn't https://github.com/bestguy/sveltestrap/pull/356 fix that issue?

missing https://github.com/bestguy/sveltestrap/blob/master/src/Tooltip.svelte#L3
Probably not. Or i'm doing something wrong during npm run dist in node_modules\sveltestrap

@bestguy is possible to update deps?
<EMAIL_ADDRESS>benmccann fix modules export
@2.11.0 svg support

@bato3 have you considered forking and using your fork instead? It looks like the repo is not very active atm :/

I'm also getting this error in SvelteKit. Ping @bestguy. I'd love a fix, updating the above dependencies.

A current workaround that I used is using the fork by laxadev. It's working fine without any errors and it can be installed by running npm i git+https://github.com/laxadev/sveltestrap.git.

ah nice! I made my own fork integrating some of the PRs of this repo  yet to be merged but I'll give @laxadev 's fork a try. Thanks @ynshung

I'm having the same issue.  Really don't want to build a Svelte app with Sveltestrap.  Have posted both there and on popper github.

If I add:
  "type": "module",

to @popperjs/core/package.json, I can run without errors. So sveltestrap imports the ESM version of popper but because its package.json is generic and the ESM files do not end in .mjs, we get the error.

This helped me get rid of the error

Dear @bestguy, can you please provide a quick statement if you will support SvelteKit short-term?
It seems an update "Popper is now Floating UI!" should easily solve the issue.
Otherwise we SvelteKit users need to look for a stable fork that works with SvelteKit. Thanks!

Same issue here

@bato3, @bluepuma77, @HeyAvi, @jtlapp, @king612, @laxadev, @nstuyvesant, @skrenes , @ynshung
I really hope @bestguy is ok :pray:.
The "situation" is not evolving and it's been almost 2 months since the last commit on this repo. I think we should "agree" on choosing an "official" fork for us to use. Any volunteer? :grimacing: Or which of the current 150+ forks could be a good candidate?
I think it is time to take a decision, but organizing this through github issues is probably not ideal. Maybe we could use Svelte's discord to discuss this?
What's your take on all this?
Thanks.

@bato3, @bluepuma77, @HeyAvi, @jtlapp, @king612, @laxadev, @nstuyvesant, @skrenes , @ynshung I really hope @bestguy is ok 🙏.
The "situation" is not evolving and it's been almost 2 months since the last commit on this repo. I think we should "agree" on choosing an "official" fork for us to use. Any volunteer? 😬 Or which of the current 150+ forks could be a good candidate? I think it is time to take a decision, but organizing this through github issues is probably not ideal. Maybe we could use Svelte's discord to discuss this? What's your take on all this?
Thanks.

Yes, let's hope everything is OK with @bestguy
I only fixed this issue on my fork but I'm not planning to maintain/fix any other problems there.
So, yes. It would be good to find someone who is going to keep updating/fixing this repo.
For me, discord is fine to continue this discussion or whatever anyone else prefers.
I hope there is someone who will keep this alive. 🙏

I too hope that @bestguy is okay. I wish I could commit to supporting a fork, but I'm overwhelmed this year. These last couple months, I've been getting by thanks to the suggestion from @nstuyvesant. I've made it convenient by using sed that basically checks if the version is still 2.11.5 and then adds the module type to package.json. It's such a bandaid :/
sed -i '/2\.11\.5/a \ \ "type": "module",'<EMAIL_ADDRESS>

The issue can be worked around by adding the following to vite.config.js
    ssr: { noExternal: ['@popperjs/core'] }

The issue can be worked around by adding the following to vite.config.js
    ssr: { noExternal: ['@popperjs/core'] }

this doesn't work. only way to remove it is to add type: "module" in the package.json of the @properjs/core/

Another temporal option with SPA mode
https://github.com/sveltejs/kit/tree/master/packages/adapter-static#spa-mode

As someone starting with Svelte and SvelteKit alongside it, what can someone do about this?
Is the only solution really just manually adding the type: module to the package.json / using someone elses repo who did that already?

@MrVauxs, over the course of developing an app with SvelteStrap, I encountered problem after problem, working at length to resolve each. When the problems were finally gone, so was SvelteStrap. Reddit is full of similar stories. I suspect you have to abide by some rigid coding philosophy to successfully build with SvelteStrap, but I was unable to figure out what that philosophy is. I ended up building my own components from vanilla bootstrap.

As someone starting with Svelte and SvelteKit alongside it, what can someone do about this? Is the only solution really just manually adding the type: module to the package.json / using someone elses repo who did that already?

Update your vite.config.js - add ssr-block :
export default defineConfig({
	plugins: [sveltekit()],
	test: {
		include: ['src/**/*.{test,spec}.{js,ts}']
	},
	ssr: {
		noExternal: ['@popperjs/core']
	}
});


Password Strength helper

Existing helper class created, PasswordStrength, which should use configuration to determine minimum password strength and return friendly results as required.

This is handled by ASP.NET Identity


Update client.py : Adding missing arg "best_of" in generate_stream fu…

…nction
Missing the "best_of" arg in generate_stream function
What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

Best of is not supported when streaming tokens.


[Helm install] ImagePullSecret does not apply to charts that doen't use serviceaccounts

Describe the bug
Istio Helm Charts applies ImagePullSecrets to ServiceAccount and the deployment(statefulset) that uses the serviceaccount inherits the ImagePullSecret from the serviceaccount.
The problem is imagePullSecrets isn't applied for components (i.e. grafana, servicegraph, tracing)  that doesn't use serviceaccounts. (Since its basically uses the default serviceaccount).
And the pods states are in ImagePullErr.
Expected behavior
ImagePullSecrets must be applied to all components of istio for users that use private image repository.
Steps to reproduce the bug
Install istio through helm with ImagePullSecret values.
helm install istio --name istio --namespace istio-system --set global.imagePullSecrets={privateregistrysecret}
Environment
Kubernetes on BM
Version
kubernetes version: 1.10.3
istio version: 1.0.0
There were a couple of workaround to make it work for my environment (Using private registry)

Simply add imagePullSecrets to deployments that doen't need RBAC (serviceaccounts)

Adjust the template in install/kubernetes/helm folder

Add imagePullSecrets to the default service-account.

I'll put in a PR with the changes I made to the deployment template

#7560

Closing due to PR merge


Add ability to rename teams

Not high-priority but should be easy to implement, so I'll take care of this soon.


Add a util function to auth module to retrieve data in authentication context

Description:
There are utility/convenient functions in the auth module to populate the authentication context[1][2] which is part of InvocationContext [3]. I would like to suggest let's have some util function(s) retrieve these also.
[1] https://v1-0.ballerina.io/learn/api-docs/ballerina/auth/functions.html#setAuthenticationContext
[2] https://v1-0.ballerina.io/learn/api-docs/ballerina/auth/functions.html#setPrincipal
[3] https://v1-0.ballerina.io/learn/api-docs/ballerina/runtime/records/InvocationContext.html
Steps to reproduce:
N/A
Affected Versions:
1.0.1, 1.0.0
OS, DB, other environment details and versions:
MacOS/ JDK 1.8
Related Issues (optional):
Suggested Labels (optional):
Improvement/suggestion/idea
Suggested Assignees (optional):
@wggihan @ldclakmal

These utils are now refactored with the PR [1]. With that change there are 2 APIs to retrieve the invocation context as auth:getInvocationContext();, runtime:getInvocationContext(). Please reopen the issue if there are any concerns.
[1] https://github.com/ballerina-platform/ballerina-lang/pull/24629


Started working on a more modern and (hopefully) better looking design

I've started to work on modernizing and improving the design of the web UI. Mainly making the design slightly flatter, adding some paddings, and brighten up the design slightly (mainly because the current background is so dark, that it's hard to use darker colors to emphasize other elements). I've also changed so that the page width can go up to 1200px if there's room (previously it was fixed to 1000px).
Also, I updated the logo with one with text, but I've made it smaller. I think it looks better, and with the increased page width, and a slightly more narrow logo, it works pretty well.
It's a work in progress. This is what it currently looks like:

Compared to:

There's still a couple of more things that I'd like to fix:

[x] Change colors of the modal dialogs
[ ] Make the start and stop buttons slightly flatter, and retina (probably by not using an image)
[ ] Make the reset stats link into a button (that matches the stop button)

@heyman you are doing some awesome work! :1st_place_medal:

I think this is ready to be merged now. There's definitely more tweaks that can be done, but overall I think it's an improvement. Once it's merged, I'll update #539 to make sure that the charts looks good in the new design as well.
Here are the latest changes: