From: Gary Thomas <gary@mlbassoc.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Over-exuberant error printing?
Date: Thu, 26 May 2011 16:05:13 -0600 [thread overview]
Message-ID: <4DDECE99.70109@mlbassoc.com> (raw)
In-Reply-To: <4DDECCE7.4010501@linux.intel.com>
On 05/26/2011 03:57 PM, Darren Hart wrote:
>
>
> On 05/24/2011 09:13 AM, Gary Thomas wrote:
>> Building from today's master (3504c3a9b1af5a3405e0a03a5ade50b82535b6dd)
>> if I get an error, I get two lines printed for each real line, e.g.
>> | ERROR: The stack trace of python calls that resulted in this exception/failure was:
>> | ERROR: The stack trace of python calls that resulted in this exception/failure was:
>> | ERROR: File "sstate_task_postfunc", line 10, in<module>
>> | ERROR: File "sstate_task_postfunc", line 10, in<module>
>> | ERROR:
>> | ERROR:
>> | ERROR: File "sstate_task_postfunc", line 4, in sstate_task_postfunc
>> | ERROR: File "sstate_task_postfunc", line 4, in sstate_task_postfunc
>> etc.
>>
>> This is new behavior - any ideas?
>>
>
> I've been seeing this as well and hadn't dug in to sort it out yet. You
> said it is new behavior, have you bisected to determine when it occured?
>
Not yet - I was mostly hoping that someone else had seen such behaviour
(as you obviously have) and verified that I'm not the only one :-)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-05-26 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:13 Over-exuberant error printing? Gary Thomas
2011-05-26 21:57 ` Darren Hart
2011-05-26 22:05 ` Gary Thomas [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=4DDECE99.70109@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.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.