From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id A7114E00D4C; Thu, 9 Jun 2016 06:30:27 -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=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.49 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5E6CFE00D45 for ; Thu, 9 Jun 2016 06:30:23 -0700 (PDT) Received: by mail-wm0-f49.google.com with SMTP id r190so3258705wmr.0 for ; Thu, 09 Jun 2016 06:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=h1UJ96wXW+Z9+aCmA/zkpVHmd0EECj2P8Qk5utj0Vpg=; b=oNfbvWHwkru1PS1p7u1KDMgcVLid8smzGC9iAYaDNcSqgKa9tC92pGTeDeTwacOwgx iQLuut2k4FZiA+GT24Rx0iohW3ka5kGmGz764ssT5i0jWVP5puN5fMCnuwk88Nhir+tb B6JF2fLciY/hrmyzfVIq+0sPsQUq3a1GqFbvUcsNxu9M7FkJZDSbPXYEN5SGv1FP9XuE dMphrfvSRJnucVg0jcQf938+H2qNoXrbxscjuylxi0gOaBQRqQmeprwEIqFS39bL/YFc KyyllQe1PXHXR9Ma6p6wblWkkpSdUfw2JHlzTAJ/mLKQF4LdJBZH3N2E/r91XBJdKbQA IDUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=h1UJ96wXW+Z9+aCmA/zkpVHmd0EECj2P8Qk5utj0Vpg=; b=lrZbqXuF6Mw1ghTgK+oHkk+KyZ07keL3Ri1ktFcjMDXSRaMW6qRU8IC9NnAFceXBXr XydxFVlatsD996XWHduAHHGGtgT/EZGqn2C4XAKMm0KPNGMDCDE1lEXcgm4s/28GBjX6 lYJmryAfzgEbaWDmB4AKtVeMpQKudYHvIhNTOOxs3uoUYdKTuNjq2kbhjfXgTYbleEjh B974tHLwzjuJ8ZbdR+wCe0sq638HTp0IeZ2eh/ytjPXS0QkD5bCPpF7Adz/Oz4a3Dkj1 5g1c3BuCuOGns8CU098CaqpSVgGxacf2MkvpWE+6g/UL04PI99hj0msFemi+RJViHBSH mRww== X-Gm-Message-State: ALyK8tLPs9hBM9W6GCgMwN1ZrDOAlqPBSSzZ95RJlUcDJ6PeLOqAQKzmc73ZKCI4AoQtAx/A X-Received: by 10.28.165.66 with SMTP id o63mr10733985wme.102.1465479022323; Thu, 09 Jun 2016 06:30:22 -0700 (PDT) Received: from [192.168.2.143] ([83.217.123.106]) by smtp.googlemail.com with ESMTPSA id y6sm30388916wmy.8.2016.06.09.06.30.21 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2016 06:30:21 -0700 (PDT) To: toaster@yoctoproject.org References: From: Michael Wood Message-ID: <57596F6C.9040006@intel.com> Date: Thu, 9 Jun 2016 14:30:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: [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: Thu, 09 Jun 2016 13:30:27 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Thanks - pushed to toaster-next On 28/04/16 14:15, Barros Pena, Belen wrote: > > On 25/04/2016 16:26, "toaster-bounces@yoctoproject.org on behalf of Elliot > Smith" elliot.smith@intel.com> wrote: > >> 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/fa >> iled_builds-8440-v6 > This works for me. Thanks! > > Belén > >> 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. >> >> -- >> _______________________________________________ >> toaster mailing list >> toaster@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/toaster