Skip to content

[WIP] DON'T REVEW Jv run perf scale using comment get diagnostic bundle#77558

Open
JoukoVirtanen wants to merge 10 commits intoopenshift:mainfrom
JoukoVirtanen:jv-run-perf-scale-using-comment-get-diagnostic-bundle
Open

[WIP] DON'T REVEW Jv run perf scale using comment get diagnostic bundle#77558
JoukoVirtanen wants to merge 10 commits intoopenshift:mainfrom
JoukoVirtanen:jv-run-perf-scale-using-comment-get-diagnostic-bundle

Conversation

@JoukoVirtanen
Copy link
Copy Markdown
Contributor

Mostly for testing, but maybe will try to get this merged.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JoukoVirtanen
Once this PR has been reviewed and has the lgtm label, please assign yu-teo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 requested review from israel-hdez and msugakov April 8, 2026 18:04
@openshift-ci openshift-ci bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Apr 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing /verify-owners in a comment.

  • RTann
    • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
    • ci-operator/step-registry/stackrox/stackrox/perf-scale-post/OWNERS
  • mtesseract
    • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
    • ci-operator/step-registry/stackrox/stackrox/perf-scale-post/OWNERS

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@JoukoVirtanen: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-stackrox-stackrox-jv-run-perf-scale-using-comment-get-diagnostic-bundle-perf-scale-24nodes-scale-test stackrox/stackrox presubmit Presubmit changed
pull-ci-stackrox-stackrox-master-perf-scale-24nodes-scale-test stackrox/stackrox presubmit Presubmit changed
periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test N/A periodic Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@JoukoVirtanen
Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-stackrox-stackrox-jv-run-perf-scale-using-comment-get-diagnostic-bundle-perf-scale-24nodes-scale-test

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@JoukoVirtanen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@JoukoVirtanen
Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-stackrox-stackrox-jv-run-perf-scale-using-comment-get-diagnostic-bundle-perf-scale-24nodes-scale-test

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@JoukoVirtanen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 9, 2026

@JoukoVirtanen: all tests passed!

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.

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

Labels

do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants