From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-f54.google.com (mail-yh0-f54.google.com [209.85.213.54]) by mail.openembedded.org (Postfix) with ESMTP id E169365C7B for ; Thu, 22 Jan 2015 16:39:35 +0000 (UTC) Received: by mail-yh0-f54.google.com with SMTP id 29so1166379yhl.13 for ; Thu, 22 Jan 2015 08:39:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0jlY3JeBCRxtzzLc47rdlNAGqaLiGWn5CIES3fXIXJ8=; b=0yxqSpDOqMKUnD9CM5EN6G7Hqvxsk8FqNcMY9QAREZMkiw4T2XNWMeLA2bVDSFJzkM f4Ssepd6H76+2H/kM7gSl1JfNJqNk0wyWHcxYs0+EAAkOlIzYMjOPKx0iZBJxr6uA9ww KSkY+1winRM0qTEcIyp1YoYDIr/pW+DN750L3mID530er3xwzTR9Sda80tEBzh8K3ki1 jpzcd2hKsjCV5j15iWtXEMYQs4YJpykIkCub9g7kgck71Gj0RkQjuyF/mrW03ONGNeWj izbRaVgLwbc6KJgZq97GVFXv96aKKTY6bEGV30aCnRorGd0UaEYQHYNyHJEuJt9Bg4s4 uOhQ== X-Received: by 10.170.170.134 with SMTP id m128mr1570760ykd.21.1421944776022; Thu, 22 Jan 2015 08:39:36 -0800 (PST) MIME-Version: 1.0 Sender: kergoth@gmail.com Received: by 10.170.190.16 with HTTP; Thu, 22 Jan 2015 08:39:15 -0800 (PST) In-Reply-To: <1421938639.19798.17.camel@linuxfoundation.org> References: <1421938639.19798.17.camel@linuxfoundation.org> From: Christopher Larson Date: Thu, 22 Jan 2015 09:39:15 -0700 X-Google-Sender-Auth: BTvjP81b6yhnDwDkAmi10NGZ05s Message-ID: To: Richard Purdie Cc: bitbake-devel , "Eggleton, Paul" Subject: Re: Lifecycle issues in Bitbake X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 16:39:38 -0000 Content-Type: multipart/alternative; boundary=001a113a310c43e0be050d405131 --001a113a310c43e0be050d405131 Content-Type: text/plain; charset=UTF-8 On Thu, Jan 22, 2015 at 7:57 AM, Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > Looking at and thinking about: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5187 > > We have several issues. Firstly, DATE and TIME are locked in stone when > the base configuration is parsed. This may cause images to overwrite > previous versions for example if DATE and TIME are not re-evaluated. We > could fix this by specifically setting DATE and TIME in bitbake at > BuildStart? > Seems quite reasonable to me. Secondly, there is one cooker log file opened for the duration of the > cooker lifecycle. This is a cooker log, not a log of each build so that > is perhaps not surprising (and is the core problem in the above bug). > There is no overwriting of the log file, it just keeps growing with each > build. > > We could trigger knotty to write out build specific log files based on > the BuildStart/Finish events? > This doesn't seem unreasonable, though a build isn't necessarily bound to a particular UI, is it? Should that go into the server or perhaps the ui helper at least? Hmm. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics --001a113a310c43e0be050d405131 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Thu, Jan 22, 2015 at 7:57 AM, Richard Purdie <richard.= purdie@linuxfoundation.org> wrote:
Looking at= and thinking about:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=3D5187
We have several issues. Firstly, DATE and TIME are locked in stone when
the base configuration is parsed. This may cause images to overwrite
previous versions for example if DATE and TIME are not re-evaluated. We
could fix this by specifically setting DATE and TIME in bitbake at
BuildStart?

Seems quite reasonabl= e to me.=C2=A0

Secondly, there is one cooker log file opened for the duration of the
cooker lifecycle. This is a cooker log, not a log of each build so that
is perhaps not surprising (and is the core problem in the above bug).
There is no overwriting of the log file, it just keeps growing with each build.

We could trigger knotty to write out build specific log files based on
the BuildStart/Finish events?

This do= esn't seem unreasonable, though a build isn't necessarily bound to = a particular UI, is it? Should that go into the server or perhaps the ui he= lper at least? Hmm.
--
Christ= opher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedd= ed, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Gr= aphics
--001a113a310c43e0be050d405131--