Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SPLAT-856: [release-4.11] include storage and must-gather tests in expectedTestCount #27494

Merged
merged 1 commit into from
Dec 3, 2022
Merged

SPLAT-856: [release-4.11] include storage and must-gather tests in expectedTestCount #27494

merged 1 commit into from
Dec 3, 2022

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #27356

/assign rvanderp3

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 25, 2022
Merged
@openshift-ci openshift-ci bot requested review from bparees and csrwng October 25, 2022 12:43
@mtulio
Copy link
Contributor

mtulio commented Oct 25, 2022

/retest ci/prow/e2e-gcp-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2022

@mtulio: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws-fips
  • /test e2e-aws-image-registry
  • /test e2e-aws-jenkins
  • /test e2e-aws-serial
  • /test e2e-gcp
  • /test e2e-gcp-builds
  • /test e2e-gcp-image-ecosystem
  • /test e2e-gcp-upgrade
  • /test images
  • /test lint
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test e2e-agnostic-cmd
  • /test e2e-aws
  • /test e2e-aws-cgroupsv2
  • /test e2e-aws-csi
  • /test e2e-aws-csi-migration
  • /test e2e-aws-disruptive
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-proxy
  • /test e2e-aws-single-node
  • /test e2e-aws-single-node-serial
  • /test e2e-aws-single-node-upgrade
  • /test e2e-aws-upgrade
  • /test e2e-azure
  • /test e2e-gcp-csi
  • /test e2e-gcp-disruptive
  • /test e2e-gcp-fips-serial
  • /test e2e-gcp-ovn-rt-upgrade
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-metal-ipi-serial
  • /test e2e-metal-ipi-serial-ovn-ipv6
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-openstack
  • /test e2e-openstack-serial
  • /test e2e-vsphere
  • /test okd-e2e-gcp

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-origin-release-4.11-e2e-agnostic-cmd
  • pull-ci-openshift-origin-release-4.11-e2e-aws-cgroupsv2
  • pull-ci-openshift-origin-release-4.11-e2e-aws-csi
  • pull-ci-openshift-origin-release-4.11-e2e-aws-fips
  • pull-ci-openshift-origin-release-4.11-e2e-aws-serial
  • pull-ci-openshift-origin-release-4.11-e2e-aws-single-node
  • pull-ci-openshift-origin-release-4.11-e2e-aws-single-node-upgrade
  • pull-ci-openshift-origin-release-4.11-e2e-gcp
  • pull-ci-openshift-origin-release-4.11-e2e-gcp-csi
  • pull-ci-openshift-origin-release-4.11-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-release-4.11-e2e-gcp-upgrade
  • pull-ci-openshift-origin-release-4.11-e2e-metal-ipi-serial-ovn-ipv6
  • pull-ci-openshift-origin-release-4.11-images
  • pull-ci-openshift-origin-release-4.11-lint
  • pull-ci-openshift-origin-release-4.11-verify
  • pull-ci-openshift-origin-release-4.11-verify-deps

In response to this:

/retest ci/prow/e2e-gcp-upgrade

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/test-infra repository.

@mtulio
Copy link
Contributor

mtulio commented Nov 1, 2022

/retest-required

2 similar comments
@mtulio
Copy link
Contributor

mtulio commented Nov 3, 2022

/retest-required

@mtulio
Copy link
Contributor

mtulio commented Nov 10, 2022

/retest-required

@mtulio
Copy link
Contributor

mtulio commented Nov 22, 2022 •
edited
Loading

@bparees would you mind approving this backport related to #27356 ?

The job ci/prow/e2e-aws-single-node-upgrade seems not to have a good success ratio and also seems not to be related with this change.

xref: https://issues.redhat.com/browse/SPLAT-856

@bparees
Copy link
Contributor

bparees commented Nov 22, 2022

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Nov 22, 2022
@mtulio
Copy link
Contributor

mtulio commented Nov 24, 2022

@bparees it seems there is an open(WIP) issue to stabilize the test e2e-aws-single-node-upgrade which is currently permafailing.
Would it be a candidate to skip it?
cc @rvanderp3

@bparees
Copy link
Contributor

bparees commented Nov 28, 2022

@bparees it seems there is an open(WIP) issue to stabilize the test e2e-aws-single-node-upgrade which is currently permafailing.
Would it be a candidate to skip it?

Yup, thanks for doing the due diligence.

/override ci/prow/e2e-aws-single-node-upgrade

@bparees bparees 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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 28, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2022

@bparees: Overrode contexts on behalf of bparees: ci/prow/e2e-aws-single-node-upgrade

In response to this:

@bparees it seems there is an open(WIP) issue to stabilize the test e2e-aws-single-node-upgrade which is currently permafailing.
Would it be a candidate to skip it?

Yup, thanks for doing the due diligence.

/override ci/prow/e2e-aws-single-node-upgrade

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/test-infra repository.

@mtulio
Copy link
Contributor

mtulio commented Dec 3, 2022 •
edited by openshift-ci bot
Loading

/retitle SPLAT-856: [release-4.11] include storage and must-gather tests in expectedTestCount

@openshift-ci openshift-ci bot changed the title [release-4.11] include storage and must-gather tests in expectedTestCount SPLAT-856: [release-4.11] include storage and must-gather tests in expectedTestCount Dec 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2022 •
edited
Loading

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

SPLAT-856: [release-4.11] include storage and must-gather tests in expectedTestCount

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Dec 3, 2022
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: No Jira bug is referenced in the title of this pull request.
To reference a bug, add 'OCPBUGS-XXX:' to the title of this pull request and request another bug refresh with /jira refresh.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

This is an automated cherry-pick of #27356

/assign rvanderp3

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/test-infra repository.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3538c62 and 2 for PR HEAD bc3073a in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2022

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit f61477f into openshift:release-4.11 Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bparees bparees Awaiting requested review from bparees

@csrwng csrwng Awaiting requested review from csrwng

Assignees

@dgoodwin dgoodwin

@stbenjam stbenjam

@bparees bparees

@kasturinarra kasturinarra

@jadhaj jadhaj

@pamoedom pamoedom

@rvanderp3 rvanderp3

@jitendar-singh jitendar-singh

@prietyc123 prietyc123

@gangwgr gangwgr

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.