Skip to content

[release-4.16] USHIFT-3266: Increase cncf result collection timeout to 10m#3423

Closed
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-3413-to-release-4.16
Closed

[release-4.16] USHIFT-3266: Increase cncf result collection timeout to 10m#3423
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-3413-to-release-4.16

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented May 31, 2024

This is an automated cherry-pick of #3413

/assign ggiguash

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request May 31, 2024
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 31, 2024 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-3263

Details

In response to this:

This is an automated cherry-pick of #3413

/assign ggiguash

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 copejon and pmtk May 31, 2024 18:54
@ggiguash
Copy link
Contributor

ggiguash commented Jun 2, 2024 •
edited by openshift-ci bot
Loading

/retitle [release-4.16] USHIFT-3266: Increase cncf result collection timeout to 10m

@openshift-ci openshift-ci bot changed the title [release-4.16] USHIFT-3263: Increase cncf result collection timeout to 10m [release-4.16] USHIFT-3266: Increase cncf result collection timeout to 10m Jun 2, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 2, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 2, 2024 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: This pull request references USHIFT-3266 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #3413

/assign ggiguash

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.

@ggiguash
Copy link
Contributor

ggiguash commented Jun 2, 2024

/test metal-periodic-test
/test metal-periodic-test-arm
/label backport-risk-assessed

@ggiguash
Copy link
Contributor

ggiguash commented Jun 2, 2024

/lgtm
/label jira/valid-bug

@openshift-ci openshift-ci bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. labels Jun 2, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, openshift-cherrypick-robot

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 Jun 2, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Jun 2, 2024

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Jun 2, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 2, 2024

/retest-required

Remaining retests: 0 against base HEAD a56d863 and 2 for PR HEAD 3ab996f in total

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 3, 2024

/retest-required

Remaining retests: 0 against base HEAD 978c906 and 1 for PR HEAD 3ab996f in total

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 4, 2024

/retest-required

Remaining retests: 0 against base HEAD 894ac9a and 0 for PR HEAD 3ab996f in total

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 4, 2024

/hold

Revision 3ab996f was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 4, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Jun 4, 2024

/test metal-periodic-test metal-periodic-test-arm

@ggiguash
Copy link
Contributor

ggiguash commented Jun 4, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 4, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 4, 2024

/retest-required

Remaining retests: 0 against base HEAD 894ac9a and 2 for PR HEAD 3ab996f in total

@ggiguash
Copy link
Contributor

ggiguash commented Jun 4, 2024

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2024

@openshift-cherrypick-robot: 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/metal-periodic-test-arm 3ab996f link true /test metal-periodic-test-arm
ci/prow/metal-periodic-test 3ab996f link true /test metal-periodic-test

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-ci-robot
Copy link

openshift-ci-robot commented Jun 5, 2024

/retest-required

Remaining retests: 0 against base HEAD e0764a1 and 1 for PR HEAD 3ab996f in total

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 5, 2024
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jun 5, 2024

PR needs rebase.

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.

@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/close

@openshift-ci openshift-ci bot closed this Jun 5, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 5, 2024

@ggiguash: Closed this PR.

Details

In response to this:

/close

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.

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

Reviewers

@copejon copejon Awaiting requested review from copejon

@pmtk pmtk Awaiting requested review from pmtk

Assignees

@ggiguash ggiguash

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @ggiguash @openshift-merge-robot