Skip to content

TRT-2483: feat(ginkgo): add monitor tests to extension test result output #30678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
stbenjam wants to merge 1 commit into
base: main
Choose a base branch
from
Open

TRT-2483: feat(ginkgo): add monitor tests to extension test result output #30678

stbenjam wants to merge 1 commit into from
+285 −2

Conversation

@stbenjam
Copy link
Member

@stbenjam stbenjam commented Jan 12, 2026

Convert synthetic JUnit test cases to ExtensionTestResult format so monitor tests appear in the extension_test_result_e2e JSON and HTML files.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 12, 2026

Pipeline controller notification
This repo 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

@stbenjam stbenjam changed the title feat(ginkgo): add monitor tests to extension test result output TRT-2483: feat(ginkgo): add monitor tests to extension test result output Jan 12, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 12, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 12, 2026 •
edited by openshift-ci bot
Loading

@stbenjam: This pull request references TRT-2483 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.22.0" version, but no target version was set.

Details

In response to this:

Convert synthetic JUnit test cases to ExtensionTestResult format so monitor tests appear in the extension_test_result_e2e JSON and HTML files.

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.

@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial January 12, 2026 16:01
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 12, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 12, 2026

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-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@stbenjam stbenjam force-pushed the monitor branch 2 times, most recently from b377caf to 53f79a8 Compare January 12, 2026 19:37
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 12, 2026

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-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@stbenjam
Copy link
Member Author

stbenjam commented Jan 12, 2026

/test verify

@stbenjam
Copy link
Member Author

stbenjam commented Jan 13, 2026

/pipeline required

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 13, 2026

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-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@stbenjam @claude
feat(ginkgo): add synthetic and monitor tests to extension test resul…
d336cca 
…t output

Convert synthetic JUnit test cases to ExtensionTestResult format so they
appear in the extension_test_result_e2e JSON and HTML files.

Additionally, produce separate OTE artifacts for monitor tests:
- extension_test_result_monitors_*.json
- extension_test_result_monitors_*.html

The monitor HTML viewer displays "Results for monitors" as the title.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 13, 2026

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-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@stbenjam
Copy link
Member Author

stbenjam commented Jan 13, 2026

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@stbenjam: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-microshift d336cca link true /test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-microshift-serial d336cca link true /test e2e-aws-ovn-microshift-serial

Full PR test history. Your PR dashboard.

Details

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.

@openshift-trt
Copy link

openshift-trt bot commented Jan 14, 2026

Job Failure Risk Analysis for sha: d336cca

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift IncompleteTests
Tests for this run (24) are below the historical average (1389): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial IncompleteTests
Tests for this run (24) are below the historical average (752): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@stbenjam @openshift-ci-robot