From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6519112020741062656 X-Received: by 10.80.184.23 with SMTP id j23mr650646ede.3.1517910219785; Tue, 06 Feb 2018 01:43:39 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.182.240 with SMTP id f45ls5211536ede.1.gmail; Tue, 06 Feb 2018 01:43:39 -0800 (PST) X-Google-Smtp-Source: AH8x226US66HnjmTn2hhtUjKSh8Ex0aXhkBgn+ugMDYm0zQpWBbAm1htvhITa5x1CX9tc4lJvbtC X-Received: by 10.80.146.139 with SMTP id k11mr659442eda.4.1517910219253; Tue, 06 Feb 2018 01:43:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517910219; cv=none; d=google.com; s=arc-20160816; b=yd5qD07p6SvsftGtK6DUaiJil18P+ky5wualdlo0Dd1quDruiQboQ7c1cuhBwQqnuB uXImkEN4iwZVKODvzj1XBRZaPb61NrWV68K8FXWJODUe+3fPRW1PYMdsuvxtk0v4qUDa igOOhjdLi0Tbvem0Lav2jrGqfWLDOy0cY+mCsMgGAxZ2k9m17QXpctHOA6tPgtsopCTE V+aL8sLi4x8+jCB1Q4DGg1JjhQ4hIJ33sal3Gu0ZVKtNcQrn7FSzVJAYAg4mVOIi+F8Z jFnlEnJXym/Chy1xbyK515aRe5jCDXp69v5rXJrRnjSMStxY9/PlFwKKJifCaCGzgRz6 t8PQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=ZclBjqBjUpTOq3HDnX8Z7uvd+bspbPWUAp2ShqJj0VA=; b=wUfs7VaiBY4uSG6EwV7fBByR9E6qkCzCNErwOvhmIJqH9oZNmZBrBJqnSbPvGbxxDx 02cLv+rkbDucEwTk6DqNTdFlOxSfVkmBhtkGrS2jzSFX6NWB0M648Mgtuo7oeElJXQ44 n4ZFYDGj0traaqnxi5F//t6eVjMAmSUJXpk6KM1QvozzKjtz7XM++wt5V0JZl6zfEEaF Y5wQRfQyaEUMK6W0Bt5M1O9jE31A2P15A8l7Iz7Er10Lp8gI3j7ZhSYVy3JzrIK/jckJ QiTdHp5ZW67O8XtEDGF0Td5mpkUZz4jllbCqoMShCOGSzbzr6Ku4r8sMGA02xARPOHOD +gSQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id t4si815471edt.2.2018.02.06.01.43.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 01:43:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w169hZeh028604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 6 Feb 2018 10:43:37 +0100 Subject: Re: [PATCH 2/2] buildchroot: Permanently mount '/dev', '/sys' and '/proc' To: Jan Kiszka , isar-users@googlegroups.com References: <20180205164347.28375-1-asmirnov@ilbers.de> <20180205164347.28375-3-asmirnov@ilbers.de> <604637ca-63f4-524a-0484-34f38f706919@siemens.com> <4364b432-f199-d2f7-3d26-32b0cfc91c0b@siemens.com> From: Alexander Smirnov Message-ID: <4f6333ae-f27f-b742-157e-d94623c8b517@ilbers.de> Date: Tue, 6 Feb 2018 12:43:30 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <4364b432-f199-d2f7-3d26-32b0cfc91c0b@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: lqusxLdcGwyD On 02/06/2018 12:38 PM, Jan Kiszka wrote: > On 2018-02-05 19:06, Jan Kiszka wrote: >>>> And when I restart the build that I interrupt after buildchroot was long >>>> finished, that task is still rebuild - and that fails, maybe because of >>>> preexisting artifacts. >>> >>> That's the known problem, we have no do_clean task implemented. Re-run >>> on existing tree is not officially supported for now. >> >> That should be fixed, or our turn-around times for Isar development will >> explode! > > This is really an urgent must-fix. I'm doing full rebuilds over and over > again now, just to test small changes down the pipeline. > > Do you already have an idea how to prevent the buildchroot rebuild? I > suppose it's caused by the new prepare task, right? Can we achieve that > without invalidating the buildchroot setup? That's unexpected bitbake behavior for me, I didn't assume that it invalidates all the stamps starting from the current. :-( Will fix this now. Alex