TRT-2275: introduce cluster health-check subcommand for openshift-tests #30211
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@jianlinliu: This pull request references TRT-2275 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jianlinliu The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial openshift/release#68971 |
|
@jianlinliu: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info. |
|
/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial openshift/release#68971 |
|
@jianlinliu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/cc707b60-8c63-11f0-9d46-ba5c41f4bd3d-0 |
|
/retest ci/prow/e2e-aws-disruptive |
|
@jianlinliu: The The following commands are available to trigger optional jobs: Use In response to this:
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. |
|
/test e2e-aws-disruptive |
|
/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial openshift/release#68971 |
|
@jianlinliu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2b4ad870-8c90-11f0-8f25-7cc7bbfb9a70-0 |
|
Job Failure Risk Analysis for sha: ced8f53
|
|
Job Failure Risk Analysis for sha: 320c966
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 320c966
New tests seen in this PR at sha: 320c966
|
jianlinliu
force-pushed
the
TRT-2275
branch
from
6e73312 to
ef8d867
Compare
pkg/e2eanalysis/e2e_analysis.go
Outdated
| } | ||
| fmt.Println(string(out)) | ||
| if opt.JUnitDir != "" { | ||
| filePrefix := "e2e-analysis" |
There was a problem hiding this comment.
I didn't think about it earlier but this should be junit_e2e_analysis to get picked up automatically as junit output like junit_e2e__20250912-053909.xml
There was a problem hiding this comment.
Sure. One more question, will e2e-monitor-tests__20250912-053909.xml in the same folder also get picked up automatically ? I am wondering what will pick it up for what purpose ?
|
Job Failure Risk Analysis for sha: ef8d867
|
jianlinliu
force-pushed
the
TRT-2275
branch
from
ef8d867 to
f15d297
Compare
|
@jianlinliu: The following tests failed, say
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. |
|
Is there a reason to not just make these proper ginkgo tests in their own suite? You'd just then run the suite |
|
Job Failure Risk Analysis for sha: f15d297
|
No description provided.