Repository navigation
Conversation
|
Pipeline controller notification This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration. Use |
|
@dtantsur: This pull request references METAL-1977 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 task to target the "5.1.0" version, but no target version was set. DetailsIn 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. |
|
Hello @dtantsur! Some important instructions when contributing to openshift/api: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to
|
|
CI has picked up a code generation issue. Otherwise LGTM |
16708c2 to
b957faf
Compare
|
/lgtm |
|
Scheduling tests matching the |
b957faf to
09e4df9
Compare
|
Chai test selection for
Reason: PR adds a new |
|
/pipeline mark-pipeline-gate 09e4df9 |
|
/verified later @dtantsur |
|
@dtantsur: This PR has been marked to be verified later by DetailsIn 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. |
|
/pipeline required |
|
The controller does not dispatch second-stage tests in agentic mode. Use |
|
@redhat-chai-bot can you make the jobs actually run? The PR is blocked. |
|
/pipeline skip-agentic-mode |
|
Traditional pipeline scheduling is enabled for this PR and future pushes. Running tests are unchanged. |
|
/pipeline required |
|
Scheduling tests matching the |
|
The earlier required-pipeline request was not queued because this PR was in agentic mode. I switched this PR to traditional pipeline scheduling and retried the required pipeline; the merge bot confirmed scheduling is enabled and announced the second-stage test selections. The latest check snapshot still shows 15 pending checks (16 passed, 0 failed), so the tests have been scheduled but have not completed yet. AI-generated. Review for accuracy. |
|
/hold Revision 09e4df9 was retested 3 times: holding |
|
/hold cancel Stupid bot (or our stupid policies?) |
See openshift/enhancements#2118 for details. Signed-off-by: Dmitry Tantsur <dtantsur@protonmail.com>
09e4df9 to
d5a84d0
Compare
|
/lgtm |
|
Scheduling tests matching the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: everettraven, JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@dtantsur: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
See openshift/enhancements#2118 for details.
Signed-off-by: Dmitry Tantsur dtantsur@protonmail.com