From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.analogue-micro.com (mail.analogue-micro.com [217.144.149.242]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 49C21E0144E for ; Thu, 20 Jun 2013 03:25:22 -0700 (PDT) Received: by mail.analogue-micro.com (Postfix, from userid 999) id 4424968A01B; Thu, 20 Jun 2013 11:25:21 +0100 (BST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on loki.analogue-micro-ltd.com X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable version=3.3.2 Received: from [192.168.12.145] (phobos.analogue-micro-ltd.com [192.168.12.145]) by mail.analogue-micro.com (Postfix) with ESMTP id CA58D68A01A; Thu, 20 Jun 2013 11:25:19 +0100 (BST) Message-ID: <51C2D88F.5030900@mlbassoc.com> Date: Thu, 20 Jun 2013 11:25:19 +0100 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Yocto Project References: <51C291AF.1070508@mlbassoc.com> In-Reply-To: <51C291AF.1070508@mlbassoc.com> Subject: Re: Build doesn't interrupt cleanly X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jun 2013 10:25:23 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2013-06-20 06:22, Gary Thomas wrote: > Using Yocto master (1dd643b142c69ac9035e29bff11d02201638dc65) > > I forcefully interrupted a bitbake build with ^C^C. When it > shut down, I made some changes to my local.conf and then tried > to fire it up again, only to get this error: > ERROR: Only one copy of bitbake should be run against a build directory > > It looks like bitbake didn't totally get cleaned up in this case. > $ ps ax | grep bit > 16319 pts/4 S 0:01 python /home/local/poky-multi/bitbake/bin/bitbake-worker decafbad > > Killing this left over worker let me continue. > > I've never seen this before, so perhaps it's new behaviour. > If it happens again, I'll file a bug. > Looks like this was reported as bug #4750 only yesterday :-) -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------