From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Musat, George L" <george.l.musat@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.
Date: Tue, 02 Jun 2015 12:30:36 +0100 [thread overview]
Message-ID: <1433244636.404.191.camel@linuxfoundation.org> (raw)
In-Reply-To: <042E875E1B5D414CA9BB78B7D4FA691C2671384A@IRSMSX107.ger.corp.intel.com>
On Tue, 2015-06-02 at 09:50 +0000, Musat, George L wrote:
> Hi Richard,
>
> Are you sure it's this patches fault for that? I only added some more
> errors to the lists. Also I tested the patch locally and runs fine on
> qemux86 master. For the Centos it looks like a network problem
> occurred half way into the tests.
I saw the same error locally, when I reverted the patch it went away so
I'm pretty sure it was from this patch, yes.
Cheers,
Richard
prev parent reply other threads:[~2015-06-02 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 11:29 [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist Lucian Musat
2015-05-30 21:26 ` Richard Purdie
2015-06-02 9:50 ` Musat, George L
2015-06-02 11:30 ` Richard Purdie [this message]
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=1433244636.404.191.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=george.l.musat@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.