openshift
add psi performance test
Pipeline controller notification
This repository is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.
For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.
This repository is configured in: automatic mode
Scheduling required tests: /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: cpmeadors, qiliRedHat Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@qiliRedHat: all tests passed!
Full PR test history. Your PR 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-sigs/prow repository. I understand the commands that are listed here.
@dgoodwin I hope to get the merged before team year end shutdown. If there is any comment, pls let me know.
Can we get a much expanded commit message here to help reviewers and approvers get context quickly. I'm immediately confused about python and shell testing going into a golang repo with no apparent link to the junit suites and CI we normally rely on. What is this, why is it in python shell, how will it be run and results collected?
Can we get a much expanded commit message here to help reviewers and approvers get context quickly. I'm immediately confused about python and shell testing going into a golang repo with no apparent link to the junit suites and CI we normally rely on. What is this, why is it in python shell, how will it be run and results collected?
I will Qiujie update the commit message, but we discussed this and wanted to consolidate all automated testing in one place. origin seemed like the obvious place. We know it is a deviation from all tests being in the ginkgo e2e framework. Modifying the tests so they generate junit and or porting to ginkgo will be a follow on step. We are open to suggestions for alternatives.