From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2B7D4E00BC2; Mon, 30 Nov 2015 03:01:05 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [134.134.136.65 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BE191E00B99 for ; Mon, 30 Nov 2015 03:00:44 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 30 Nov 2015 03:00:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,364,1444719600"; d="scan'208";a="861130268" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga002.jf.intel.com with ESMTP; 30 Nov 2015 03:00:43 -0800 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 30 Nov 2015 11:00:40 +0000 Received: from irsmsx110.ger.corp.intel.com ([169.254.15.163]) by irsmsx111.ger.corp.intel.com ([169.254.2.223]) with mapi id 14.03.0248.002; Mon, 30 Nov 2015 11:00:41 +0000 From: "Barros Pena, Belen" To: Paul Eggleton Thread-Topic: [Toaster] Toaster, buildstats and build history Thread-Index: AQHRKQNIEIcJ/0WMZkS/u6f2vWKmjJ6ziSuAgADhfwA= Date: Mon, 30 Nov 2015 11:00:39 +0000 Message-ID: References: <16100472.iIHbaHrMSf@peggleto-mobl.ger.corp.intel.com> In-Reply-To: <16100472.iIHbaHrMSf@peggleto-mobl.ger.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.8.151023 x-originating-ip: [10.237.224.34] MIME-Version: 1.0 Cc: "toaster@yoctoproject.org" Subject: Re: Toaster, buildstats and build history X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 11:01:05 -0000 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-ID: <5C24AD9D6590FC4E998F3FFA21299904@intel.com> Content-Transfer-Encoding: quoted-printable On 29/11/2015 21:33, "Paul Eggleton" wrote: >Hi Belen, > >On Friday 27 November 2015 11:03:45 Barros Pena, Belen wrote: >> On 27/11/2015 00:34, "openembedded-core-bounces@lists.openembedded.org >>on >> behalf of Paul Eggleton" >>> on behalf of paul.eggleton@linux.intel.com> wrote: >> >On Wednesday 25 November 2015 10:30:28 Patrick Ohly wrote: >> >> The initial implementation of YOCTO #8138 >> >> ("buildhistory-extra.bbclass: store more information about a build") >> >> had some issues ("kconfig" file not preserved) but more importantly, >> >> additional changes are needed to support also gathering information >> >> about native recipes. >> >>=20 >> >> I am proposing to include only the "buildhistory.bbclass: support >> >> extending the content of the build history" patch into OE-core. >> >>=20 >> >> The original buildhistory-extra.bbclass and the modifications made to >> >> it are included here merely to provide the context for that change >>and >> >> to publish the modifications. >> > >> >For others' reference, buildhistory-extra.bbclass was previously >>attached >> >to >> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=3D8138 - I didn't and >> >wouldn't >> >propose introducing it into OE-Core in its current form because it's >>kind >> >of >> >turning buildhistory into something it wasn't designed for, though I >> >don't >> >disagree that it's useful. Happy to hear opinions from others on this >> >though. >> > >> >One aspect that will probably change in the future is how it picks up >>the >> >kernel configuration - for >> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=3D5574 (which I hope = to >> >get to >> >for 2.1, but no promises) we will need to write the kernel >>configuration >> >to the >> >sysroot so that we have somewhere we can look for it; if that's the >>case >> >there'll be no need to copy it specially in buildhistory-extra.bbclass. >> >> There seems to be a fair bit of work going on in build history, and >>also I >> think in builstats. Toaster uses both, so I wonder: >>=20 >> 1. Will the changes affect Toaster in any way? > >As far as the discussion you're quoting above, no. As I mentioned, >buildhistory-extra.bbclass isn't intended to go into OE-Core. > >> 2. Is any of the additions to build history providing extra information >> that we should display in Toaster? > >At the moment buildhistory isn't exposed in Toaster beyond how it's being >used=20 >to get information on packages and image contents. Independent of the >changes=20 >in the above quoted discussion, you could start exposing buildhistory in >Toaster, but the problem is you need to choose which build to compare it >to, We should really do this at some point. We've had a feature open in Bugzilla for ages: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3D6840 Cheers Bel=E9n >=20 >or you'll just get the last build which may not make sense in a Toaster >context. > >Cheers, >Paul > >--=20 > >Paul Eggleton >Intel Open Source Technology Centre