Skip to content

[WIP] NO-ISSUE: [release-4.16] bump e2e timeout +15mins#800

Closed
perdasilva wants to merge 2 commits intoopenshift:release-4.16from
perdasilva:bumptimeout
Closed

[WIP] NO-ISSUE: [release-4.16] bump e2e timeout +15mins#800
perdasilva wants to merge 2 commits intoopenshift:release-4.16from
perdasilva:bumptimeout

Conversation

@perdasilva
Copy link
Copy Markdown
Contributor

@perdasilva perdasilva commented Jun 25, 2024

Adding junit report to see if I can better capture runtimes

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@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 25, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@perdasilva: This pull request explicitly references no jira issue.

Details

In 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.

@openshift-ci openshift-ci Bot requested review from anik120 and joelanford June 25, 2024 11:38
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 25, 2024
@grokspawn
Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, perdasilva

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

@joelanford
Copy link
Copy Markdown
Member

/backport-risk-assessed

Also manually adding cherry-pick-approved label since this is a non-functional change.

@joelanford joelanford added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jun 25, 2024
@perdasilva
Copy link
Copy Markdown
Contributor Author

/retest

@perdasilva perdasilva changed the title NO-ISSUE: [release-4.16] bump e2e timeout +15mins [WIP] NO-ISSUE: [release-4.16] bump e2e timeout +15mins Jun 26, 2024
@openshift-ci openshift-ci Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. and removed lgtm Indicates that a PR is ready to be merged. labels Jun 26, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 26, 2024

New changes are detected. LGTM label has been removed.

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 26, 2024

@perdasilva: 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-gcp-olm 3a7d188 link true /test e2e-gcp-olm
ci/prow/e2e-gcp-olm-flaky 3a7d188 link false /test e2e-gcp-olm-flaky

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.

@perdasilva perdasilva closed this Jul 1, 2024
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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants