Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.16from
ggiguash:4.16_cncf_timeout
Jun 6, 2024
Merged

[release-4.16] USHIFT-3266 Increase cncf result collection timeout to 10m#3442
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.16from
ggiguash:4.16_cncf_timeout

Conversation

@ggiguash

@ggiguash ggiguash commented Jun 5, 2024

Copy link
Copy Markdown
Contributor

Manual cherrypick of #3413

@openshift-ci openshift-ci Bot requested review from pliurh and pmtk June 5, 2024 16:00
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2024
@ggiguash

ggiguash commented Jun 5, 2024

Copy link
Copy Markdown
Contributor Author

/test microshift-metal-tests

@ggiguash

ggiguash commented Jun 6, 2024

Copy link
Copy Markdown
Contributor Author

/test microshift-metal-tests microshift-metal-tests-arm

@pacevedom

Copy link
Copy Markdown
Contributor

/test metal-periodic-test-arm

@pacevedom pacevedom left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/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 6, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2024
@openshift-ci

openshift-ci Bot commented Jun 6, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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

@ggiguash

ggiguash commented Jun 6, 2024

Copy link
Copy Markdown
Contributor Author

/label jira/valid-bug

@openshift-ci openshift-ci Bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 6, 2024
@openshift-ci

openshift-ci Bot commented Jun 6, 2024

Copy link
Copy Markdown
Contributor

@ggiguash: 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

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants