Currently, it is possible for a user to upload a notebook sample with hard-coded arbitrary experiment name to run their pipeline. However, our sample test infra adopts the convention that the experiment name should be TEST_NAME-test, which might be inconsistent with the user specified name.
Inconsistent names can cause the sample test infra fails to capture the test run result.
In response to [this](https://github.com/kubeflow/pipelines/issues/2110#issuecomment-543480309):
>/close
>Fixed by #2292 .
>Now sample test infra can override experiment name through env var.
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.
Currently, it is possible for a user to upload a notebook sample with hard-coded arbitrary experiment name to run their pipeline. However, our sample test infra adopts the convention that the experiment name should be TEST_NAME-test, which might be inconsistent with the user specified name.
Inconsistent names can cause the sample test infra fails to capture the test run result.