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.6] Bug 2028280: write to files instead of stdout #984

Merged
merged 1 commit into from Dec 3, 2021
Merged

[release-4.6] Bug 2028280: write to files instead of stdout #984

merged 1 commit into from Dec 3, 2021

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #482

/assign wking

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Dec 1, 2021
Merged
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2021

@openshift-cherrypick-robot: Bugzilla bug 1853116 has been cloned as Bugzilla bug 2028280. Retitling PR to link against new bug.
/retitle [release-4.6] Bug 2028280: write to files instead of stdout

In response to this:

[release-4.6] Bug 1853116: write to files instead of stdout

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.6] Bug 1853116: write to files instead of stdout [release-4.6] Bug 2028280: write to files instead of stdout Dec 1, 2021
@openshift-ci openshift-ci bot added the bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. label Dec 1, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2021

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2028280, 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.6.z) matches configured target release for branch (4.6.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1853116 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 1853116 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0, 4.7.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhouying7780

In response to this:

[release-4.6] Bug 2028280: write to files instead of stdout

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/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Dec 1, 2021
@wking wking mentioned this pull request Dec 1, 2021
Merged
soltysh
soltysh approved these changes Dec 3, 2021
View reviewed changes
Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/label backport-risk-assessed
/override ci/prow/test-cmd
it's known to fail in older releases

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 3, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2021

@soltysh: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • ci/prow/test-cmd

Only the following contexts were expected:

  • ci/prow/build-rpms-from-tar
  • ci/prow/e2e-agnostic-cmd
  • ci/prow/e2e-aws
  • ci/prow/e2e-aws-upgrade
  • ci/prow/images
  • ci/prow/rpm-build
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-oc-release-4.10-build-rpms-from-tar
  • pull-ci-openshift-oc-release-4.10-e2e-agnostic-cmd
  • pull-ci-openshift-oc-release-4.10-e2e-aws
  • pull-ci-openshift-oc-release-4.10-e2e-aws-upgrade
  • pull-ci-openshift-oc-release-4.10-images
  • pull-ci-openshift-oc-release-4.10-rpm-build
  • pull-ci-openshift-oc-release-4.10-unit
  • pull-ci-openshift-oc-release-4.10-verify
  • pull-ci-openshift-oc-release-4.10-verify-deps
  • tide

In response to this:

/lgtm
/approve
/label backport-risk-assessed
/override ci/prow/test-cmd
it's known to fail in older releases

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
Copy link
Contributor

openshift-ci bot commented Dec 3, 2021

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Dec 3, 2021
@soltysh
Copy link
Member

soltysh commented Dec 3, 2021

/override ci/prow/e2e-agnostic-cmd

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2021

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-agnostic-cmd

In response to this:

/override ci/prow/e2e-agnostic-cmd

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-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@kasturinarra
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 3, 2021
@openshift-merge-robot openshift-merge-robot merged commit 2c60620 into openshift:release-4.6 Dec 3, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2021

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

Bugzilla bug 2028280 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 2028280: write to files instead of stdout

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

@soltysh soltysh soltysh approved these changes

@zhouying7780 zhouying7780 Awaiting requested review from zhouying7780

@deads2k deads2k Awaiting requested review from deads2k

Assignees

@wking wking

@soltysh soltysh

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/severity-low Referenced Bugzilla bug's severity is low 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

None yet
6 participants
@openshift-cherrypick-robot @soltysh @openshift-bot @kasturinarra @wking @openshift-merge-robot