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.

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

add newline to oc process output #21984

Merged

Conversation

bverschueren
Copy link
Contributor

This is purely aesthetic, yet annoying when piped through e.g. | oc create -f -

Before:

warning: Template parameter "FOO" already defined, ignoring value from file "test.env"{
    "kind": "List",
    "apiVersion": "v1",
    "metadata": {},
2 input templates found, but only the first will be processed{ 
    "kind": "List",                                     
    "apiVersion": "v1",                           
    "metadata": {},

After:

warning: Template parameter "FOO" already defined, ignoring value from file "test.env"
{
    "kind": "List",
    "apiVersion": "v1",
    "metadata": {},
2 input templates found, but only the first will be processed
{                                                              
    "kind": "List",                                     
    "apiVersion": "v1",                           
    "metadata": {},

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 7, 2019
@openshift-ci-robot
Copy link

Hi @bverschueren. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 7, 2019
@openshift-ci-robot
Copy link

@bverschueren: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

This is purely aesthetic, yet annoying when piped through e.g. | oc create -f -

Before:

warning: Template parameter "FOO" already defined, ignoring value from file "test.env"{
   "kind": "List",
   "apiVersion": "v1",
   "metadata": {},
2 input templates found, but only the first will be processed{ 
   "kind": "List",                                     
   "apiVersion": "v1",                           
   "metadata": {},

After:

warning: Template parameter "FOO" already defined, ignoring value from file "test.env"
{
   "kind": "List",
   "apiVersion": "v1",
   "metadata": {},
2 input templates found, but only the first will be processed
{                                                              
   "kind": "List",                                     
   "apiVersion": "v1",                           
   "metadata": {},

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.

@mfojtik
Copy link
Member

mfojtik commented Feb 8, 2019

/ok-to-test
/assign @soltysh

@openshift-ci-robot openshift-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 8, 2019
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

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bverschueren, 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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2019
@soltysh
Copy link
Member

soltysh commented Feb 8, 2019

/retest

@openshift-bot
Copy link
Contributor

/retest

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

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 9e0d0b5 into openshift:master Feb 9, 2019
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. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants