On 05/31/2011 03:26 PM, Scott Garman wrote:
Hey folks,
I'd like to collect some feedback on error messages while building that
you find confusing/annoying/unhelpful. I'm going to be working on trying
to improve the situation and would like to hear from you about what
could be more helpful.
Tha
On Thu, 2011-06-09 at 12:02 +0100, Phil Blundell wrote:
> After I made a typo (mismatched quotes) in one of my recipes, my next
> bitbake run printed:
>
> Loading cache: 100%
> |###
On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> I'd like to collect some feedback on error messages while building that
> you find confusing/annoying/unhelpful. I'm going to be working on trying
> to improve the situation and would like to hear from you about what
> could be more helpfu
On Mon, 2011-06-06 at 21:53 -0700, Darren Hart wrote:
> On 06/03/2011 08:47 AM, Chris Larson wrote:
> > Heh, I used to have a personal branch where I dropped those, and also
> > removed the unnecessary NOTE: prefix. I think its a given that
> > something that doesn't indicate a warning or an error
On 06/03/2011 08:47 AM, Chris Larson wrote:
> On Fri, Jun 3, 2011 at 8:43 AM, Phil Blundell wrote:
>> On Fri, 2011-06-03 at 09:22 -0500, Mark Hatle wrote:
>>> I believe currently we have around 3-5 messages per step, and it's still too
>>> noisy -- unless you need to debug something.
>>
>> Corre
On 06/02/2011 11:10 PM, Darren Hart wrote:
o I'm seeing duplicate messages lately - no examples handy, I'll post
or open a bug next time.
Hi Darren,
Before I can file a bug for this, I'll need more details/a reproducible
test case.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto P
On Fri, Jun 3, 2011 at 8:43 AM, Phil Blundell wrote:
> On Fri, 2011-06-03 at 09:22 -0500, Mark Hatle wrote:
>> I believe currently we have around 3-5 messages per step, and it's still too
>> noisy -- unless you need to debug something.
>
> Correct. Right now, the output looks like:
>
> NOTE: Runn
On Fri, 2011-06-03 at 09:22 -0500, Mark Hatle wrote:
> I believe currently we have around 3-5 messages per step, and it's still too
> noisy -- unless you need to debug something.
Correct. Right now, the output looks like:
NOTE: Running task 613 of 728 (ID: 190,
virtual:native:/home/pb/oe/oe-cor
Op 1 jun 2011, om 00:26 heeft Scott Garman het volgende geschreven:
> Hey folks,
>
> I'd like to collect some feedback on error messages while building that you
> find confusing/annoying/unhelpful. I'm going to be working on trying to
> improve the situation and would like to hear from you abo
On Friday 03 June 2011 15:35:45 mark gross wrote:
> Well perhaps it would be easier to build a list of packages that have
> been skipped? I think the cache knows about them. Perhaps they could
> be reported to a "skipped" file or something similar?
FYI there is a patch I submitted the other day
On Wed, Jun 01, 2011 at 05:25:58PM +0100, Richard Purdie wrote:
> On Wed, 2011-06-01 at 16:06 +0100, Phil Blundell wrote:
> > On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> > > I'd like to collect some feedback on error messages while building that
> > > you find confusing/annoying/unhel
On 6/3/11 1:10 AM, Darren Hart wrote:
>
>
> On 05/31/2011 03:26 PM, Scott Garman wrote:
...
> o In general I find the default UI to be exceedingly noisy. It feels
> very much like what I would write for something I was actively
> developing - ie, something I expect to break a lot! I don't t
On Thu, 2011-06-02 at 23:10 -0700, Darren Hart wrote:
> These are maybe a bit off topic, but I'll leave it to you to decide if
> they meet the criteria for this effort.
>
> o bb.debug messages are not logged anywhere nor do they appear on the
> console with -DDD during recipe parsing (while bb.n
On 05/31/2011 03:26 PM, Scott Garman wrote:
> Hey folks,
>
> I'd like to collect some feedback on error messages while building that
> you find confusing/annoying/unhelpful. I'm going to be working on trying
> to improve the situation and would like to hear from you about what
> could be more
On Wed, 2011-06-01 at 16:06 +0100, Phil Blundell wrote:
> On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> > I'd like to collect some feedback on error messages while building that
> > you find confusing/annoying/unhelpful. I'm going to be working on trying
> > to improve the situation an
On Tue, May 31, 2011 at 03:26:21PM -0700, Scott Garman wrote:
> Hey folks,
>
> I'd like to collect some feedback on error messages while building that
> you find confusing/annoying/unhelpful. I'm going to be working on trying
> to improve the situation and would like to hear from you about what
On Wed, Jun 1, 2011 at 9:25 AM, Richard Purdie
wrote:
> On Wed, 2011-06-01 at 16:06 +0100, Phil Blundell wrote:
>> On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
>> > I'd like to collect some feedback on error messages while building that
>> > you find confusing/annoying/unhelpful. I'm goi
On Wed, 2011-06-01 at 16:06 +0100, Phil Blundell wrote:
> On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> > I'd like to collect some feedback on error messages while building that
> > you find confusing/annoying/unhelpful. I'm going to be working on trying
> > to improve the situation an
On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> I'd like to collect some feedback on error messages while building that
> you find confusing/annoying/unhelpful. I'm going to be working on trying
> to improve the situation and would like to hear from you about what
> could be more helpfu
On Tue, May 31, 2011 at 03:26:21PM -0700, Scott Garman wrote:
> Hey folks,
>
> I'd like to collect some feedback on error messages while building
> that you find confusing/annoying/unhelpful. I'm going to be working
> on trying to improve the situation and would like to hear from you
> about what
Hey folks,
I'd like to collect some feedback on error messages while building that
you find confusing/annoying/unhelpful. I'm going to be working on trying
to improve the situation and would like to hear from you about what
could be more helpful.
I'm starting to track some of these situation
21 matches
Mail list logo