opened
nrjpoddar
The HTTP wildcard listener fall through FCM was not adding the mixer v1 filter
which was causing telemetry to be missing for BlackHole/Passthrough case.
Added Mixer v1 filter for fall through FCM in HTTP
issue
created
nrjpoddar
I'm going to enable tests based on the results of the checks.
comment
created
nrjpoddar
/test unit-tests_istio
comment
created
douglas-reid
@nrjpoddar what needs to be done here?
comment
created
nrjpoddar
Time and probably understanding the failed test case. I can't follow that unit test very easily.
comment
created
douglas-reid
Still a priority for 1.6 ?  Should we pull in help?
comment
@nrjpoddar: The following test **failed**, say `/retest` to rerun all failed tests:

Test name | Commit | Details | Rerun command
--- | --- | --- | ---
unit-tests_istio | 87db2db982f48fad77b7758c322b94f6c8902794 | [link](https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/22739/unit-tests_istio/11334) | `/test unit-tests_istio`

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
This message directly preceded comment from bot *istio-testing* by author *nrjpoddar*:
I'm going to enable tests based on the results of the checks.
@nrjpoddar: The following test **failed**, say `/retest` to rerun all failed tests:

Test name | Commit | Details | Rerun command
--- | --- | --- | ---
unit-tests_istio | 7bf77dac3e4830fc06d6995d956bad325c370797 | [link](https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/22739/unit-tests_istio/11336) | `/test unit-tests_istio`

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
This message directly preceded comment from bot *istio-testing* by author *nrjpoddar*:
/test unit-tests_istio
🧭 This issue or pull request has been automatically marked as stale because it has not had activity from an Istio team member since 2020-04-23. It will be closed on 2020-06-07 unless an Istio team member takes action. Please see [this wiki page](https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager) for more information. Thank you for your contributions.


_Created by the issue and PR lifecycle manager_.
This message directly preceded comment from bot *istio-policy-bot* by author *douglas-reid*:
Still a priority for 1.6 ?  Should we pull in help?
This message directly preceded comment from bot *istio-testing* by author *nrjpoddar*:
I'm going to enable tests based on the results of the checks.
This message directly preceded comment from bot *istio-testing* by author *nrjpoddar*:
/test unit-tests_istio
This message directly preceded comment from bot *istio-policy-bot* by author *douglas-reid*:
Still a priority for 1.6 ?  Should we pull in help?