From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 336EEE0073D; Mon, 25 Apr 2016 08:26:22 -0700 (PDT) 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.24 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 99DB4E00566 for ; Mon, 25 Apr 2016 08:26:18 -0700 (PDT) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP; 25 Apr 2016 08:26:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,533,1455004800"; d="scan'208";a="791979367" Received: from mkordyl-mobl2.ger.corp.intel.com (HELO lp.ger.corp.intel.com) ([10.252.10.45]) by orsmga003.jf.intel.com with ESMTP; 25 Apr 2016 08:26:15 -0700 From: Elliot Smith To: toaster@yoctoproject.org Date: Mon, 25 Apr 2016 16:26:07 +0100 Message-Id: X-Mailer: git-send-email 1.9.3 Subject: [PATCH 0/2] Capture command-line builds which fail due to bad targets 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, 25 Apr 2016 15:26:22 -0000 Toaster currently can't catch build failures which are due to bad targets (e.g. "bitbake ecky-thump"), as the bitbake run doesn't reach the BuildStarted event in these cases. Add a new BuildInit event which fires as soon as buildTargets() or buildFile() is invoked, and make the build object at this point. When BuildStarted fires, collect layer information, build variables etc. as previously. Backwards-compatibility is maintained for jethro by still making a build object on BuildStarted events. jethro builds which fail early will therefore not be captured by the new code, but existing functionality should not be broken either. To test: 1. Start Toaster. 2. On the command-line, run a build with a bad target like "bitbake ecky-thump". 3. The build should register as a failure on the "all builds" page. The following changes since commit fb8349b97c736d6633b2d79a4003dd86f760bdb1 (toaster-next): toaster: bin/toaster Fix noweb command (2016-04-21 14:19:05 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib elliot/toaster/failed_builds-8440-v6 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=elliot/toaster/failed_builds-8440-v6 Elliot Smith (2): cooker: add BuildInit event toasterui: use BuildInit to capture builds with bad targets bitbake/lib/bb/cooker.py | 6 ++++++ bitbake/lib/bb/event.py | 6 +++++- bitbake/lib/bb/ui/buildinfohelper.py | 17 ++++++++++------- bitbake/lib/bb/ui/toasterui.py | 19 ++++++++----------- 4 files changed, 29 insertions(+), 19 deletions(-) -- 1.9.3 --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.