From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] commands: send stderr to a new pipe
Date: Wed, 21 Jun 2017 10:01:04 -0500 [thread overview]
Message-ID: <1498057264.31575.22.camel@linux.intel.com> (raw)
In-Reply-To: <CAHiDW_F6Q9aNgRz5=HntGAMJQNLiMURUDW=ym=FojmTErA30zw@mail.gmail.com>
On Wed, 2017-06-21 at 13:56 +0300, Jussi Kukkonen wrote:
> On 19 June 2017 at 17:39, <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.
>
> I wonder if this patch could be related to the strange selftest
> failures where command output seems to be missing completely, e.g.
> AssertionError: '' != 'ERROR: Unable to find any package producing
> path /not/exist'
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/349/steps/Running%20oe-selftest/logs/stdio
I double check this series on local AB and I saw green in all tests, so
I am not sure what is going on.
This patch basically separates stdout and stderr, so now tests look into
stderr for errors instead of stdout.
Leo
>
> Jussi
>
> >
> > [YOCTO #9693]
> >
> > Signed-off-by: Leonardo Sandoval
> <leonardo.sandoval.gonzalez@linux.intel.com>
> > ---
> > meta/lib/oeqa/utils/commands.py | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/lib/oeqa/utils/commands.py
> b/meta/lib/oeqa/utils/commands.py
> > index 57286fcb10..4ef0e874ff 100644
> > --- a/meta/lib/oeqa/utils/commands.py
> > +++ b/meta/lib/oeqa/utils/commands.py
> > @@ -29,7 +29,7 @@ class Command(object):
> >
> > self.defaultopts = {
> > "stdout": subprocess.PIPE,
> > - "stderr": subprocess.STDOUT,
> > + "stderr": subprocess.PIPE,
> > "stdin": None,
> > "shell": False,
> > "bufsize": -1,
> > --
> > 2.12.0
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2017-06-21 14:51 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 [this message]
2017-06-22 14:17 ` Patrick Ohly
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=1498057264.31575.22.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=jussi.kukkonen@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