Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: leonardo.sandoval.gonzalez@linux.intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] commands: send stderr to a new pipe
Date: Thu, 22 Jun 2017 16:17:33 +0200	[thread overview]
Message-ID: <1498141053.22706.4.camel@intel.com> (raw)
In-Reply-To: <20170619143936.20912-1-leonardo.sandoval.gonzalez@linux.intel.com>

On Mon, 2017-06-19 at 07:39 -0700,
leonardo.sandoval.gonzalez@linux.intel.com wrote:
> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
> 
> Do not mix the stderr into stdout, allowing test cases to query
> the specific output.

This changes the behavior of functions that are also used outside of
OE-core in a way that won't be easy to notice. I also don't think that
it is the right default. For example, for bitbake it is easier to
understand where an error occurred when stderr goes to the same stream
as stdout.

Can't you keep the current semantic and just override it explicitly in
those tests that need separate stdout/stderr?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  parent reply	other threads:[~2017-06-22 14:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 14:39 [PATCH 1/2] commands: send stderr to a new pipe leonardo.sandoval.gonzalez
2017-06-19 14:39 ` [PATCH 2/2] selftest/cases: use stderr data when querying for errors leonardo.sandoval.gonzalez
2017-06-21 10:56 ` [PATCH 1/2] commands: send stderr to a new pipe Jussi Kukkonen
2017-06-21 11:08   ` Burton, Ross
2017-06-21 15:01   ` Leonardo Sandoval
2017-06-22 14:17 ` Patrick Ohly [this message]
2017-06-22 14:58   ` Leonardo Sandoval
2017-06-22 15:14     ` Patrick Ohly
2017-06-22 15:37       ` Leonardo Sandoval
2017-06-22 15:59         ` Patrick Ohly
2017-06-22 16:18           ` Leonardo Sandoval
2017-06-22 17:39             ` Patrick Ohly
2017-06-22 20:47               ` Leonardo Sandoval
2017-06-22 21:07                 ` Patrick Ohly
2017-06-22 21:27                   ` Leonardo Sandoval
2017-06-22 16:59           ` Richard Purdie
2017-06-22 19:35             ` Patrick Ohly
2017-06-22 20:51               ` Leonardo Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1498141053.22706.4.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox