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

[release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured' #26562

Merged
merged 1 commit into from Nov 2, 2021
Merged

[release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured' #26562

merged 1 commit into from Nov 2, 2021

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #26560

/assign dgoodwin

@dgoodwin
Skip test 'clone repository using git:// protocol should clone using …
9fb2b2f 
…git:// if no proxy is configured'

Test is no longer valid as github has deprecated unauthenticated git://
access. Will be backported to all releases back to 4.6.

See https://bugzilla.redhat.com/show_bug.cgi?id=2019433 for proper fix.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Nov 2, 2021
Merged
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@openshift-cherrypick-robot: Bugzilla bug 2019516 has been cloned as Bugzilla bug 2019519. Retitling PR to link against new bug.
/retitle [release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured'

In response to this:

[release-4.8] Bug 2019516: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured'

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 openshift-ci bot changed the title [release-4.8] Bug 2019516: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured' [release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured' Nov 2, 2021
@openshift-ci openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Nov 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2019519, which is invalid:

  • expected dependent Bugzilla bug 2019516 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
  • expected dependent Bugzilla bug 2019516 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured'

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 openshift-ci bot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Nov 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
To complete the pull request process, please assign coreydaley after the PR has been reviewed.
You can assign the PR to them by writing /assign @coreydaley in a comment when ready.

The full list of commands accepted by this bot can be found 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

@dgoodwin
Copy link
Contributor

dgoodwin commented Nov 2, 2021

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@dgoodwin: This pull request references Bugzilla bug 2019519, which is invalid:

  • expected dependent Bugzilla bug 2019516 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
  • expected dependent Bugzilla bug 2019520 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
  • expected dependent Bugzilla bug 2019522 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
  • expected dependent Bugzilla bug 2019516 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
  • expected dependent Bugzilla bug 2019520 to target a release in 4.9.0, 4.9.z, but it targets "4.7.z" instead
  • expected dependent Bugzilla bug 2019522 to target a release in 4.9.0, 4.9.z, but it targets "4.6.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@dgoodwin
Copy link
Contributor

dgoodwin commented Nov 2, 2021

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@dgoodwin: This pull request references Bugzilla bug 2019519, which is invalid:

  • expected dependent Bugzilla bug 2019518 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@dgoodwin
Copy link
Contributor

dgoodwin commented Nov 2, 2021

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@dgoodwin: This pull request references Bugzilla bug 2019519, which is invalid:

  • expected dependent Bugzilla bug 2019518 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@dgoodwin
Copy link
Contributor

dgoodwin commented Nov 2, 2021

/bugzilla refresh

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@dgoodwin: This pull request references Bugzilla bug 2019519, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.z) matches configured target release for branch (4.8.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2019518 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2019518 targets the "4.9.z" release, which is one of the valid target releases: 4.9.0, 4.9.z
  • bug has dependents

In response to this:

/bugzilla refresh

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 openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Nov 2, 2021
@deads2k
Copy link
Contributor

deads2k commented Nov 2, 2021

built locally, valid bug, fixes payload promotion, confirmed there is no merge window, manually merging.

@deads2k deads2k merged commit 6a472cb into openshift:release-4.8 Nov 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2019519 has been moved to the MODIFIED state.

In response to this:

[release-4.8] Bug 2019519: Skip test 'clone repository using git:// protocol should clone using git:// if no proxy is configured'

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.

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

@adambkaplan adambkaplan Awaiting requested review from adambkaplan

@coreydaley coreydaley Awaiting requested review from coreydaley

Assignees

@dgoodwin dgoodwin

Labels
bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@openshift-cherrypick-robot @dgoodwin @deads2k