From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6521574339082452992 X-Received: by 10.80.215.210 with SMTP id m18mr419598edj.0.1518615535335; Wed, 14 Feb 2018 05:38:55 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.215.80 with SMTP id i16ls2296342edj.5.gmail; Wed, 14 Feb 2018 05:38:54 -0800 (PST) X-Google-Smtp-Source: AH8x225QNxz3ebLfDz30NqqXmwDo/Vau9RmQPthKSJEPKdJpJmbDoUQoBObU4G0PeOJJ8ZFPTCR6 X-Received: by 10.80.243.144 with SMTP id g16mr1660835edm.11.1518615534612; Wed, 14 Feb 2018 05:38:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518615534; cv=none; d=google.com; s=arc-20160816; b=JPVcNdhQ0kXNohLeRJTZTq1k3vT7JaUTz5YZvTgFC77Qdz3rJOMS6dYffpO6CXT5fE 1ch/cUPNpqnvGswyHrUrlY+Dc3jI1GZPmY3DsTBGYHsI8XvFA0+x3yqJLoBs4l3H2GMo dtXhC+k2ufrIHpY1WyGi4ekYVbnePTg0VAMYS5Mu8ZOYwxdD0ocUxmgep4RsPCqUaayq jbjreEWykJLxUoZMgFgs5BPpjiz/7cQR/eb8JkX3GuNfPH8utJuhZQBVQHYf9+YWU8gi fhpsomAJNZ4L1anDOj8oHn7vabyvcSz1f0cZW0AzMfoK8SoJ5fmiCIUmcnkX/jUi9h5R Utjw== 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:references:to:from:subject :arc-authentication-results; bh=UO0mrqXHPPV964+MurRCQpMe4FSzrqn9pCm0+Z4+9lk=; b=Fp64nzOK+PYUaZUorhh1fcqb5OyLVrBRMbmHrsImCSLZSCqNp4BZWNr565ZVzXVwBZ 9AzmrGiHY8sy2SBEQqwLkG+uCswou+hdjs+DtBX56Hr6oGJK6RjWu0Dt5S7phtTFONxx 0imhHNoggwyUQkCSg2F9HtrgKJUVjXN5lx2dBs2RGs68OT0qxdzudhKMTAipEVw3hZ5X AoNsS78pvq23FlnxG57H5lWQZI7xCjmN2IYw206iXVjTamzclOPclF1fbEYfbZfoaYAj +AV3pFesExQbSVoSvPTI08IWEl4syEKqNKmbNgFhPMx0spqeTB1Zc/Os0hJinEzfltl0 b5EA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id m19si849559edd.4.2018.02.14.05.38.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Feb 2018 05:38:54 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w1EDcsLN008190 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Feb 2018 14:38:54 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w1EDcrgP030462; Wed, 14 Feb 2018 14:38:53 +0100 Subject: Re: [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes From: Jan Kiszka To: Alexander Smirnov , isar-users References: <96a5d7df-b7a3-08ec-3c28-85ecf332d32b@siemens.com> <01a34333-06a2-4df0-a51e-17aced9f9ee3@ilbers.de> <7bd0cc56-0dba-6a04-767a-de4edcc3be1e@siemens.com> Message-ID: <96dd5116-fc00-d5df-d48b-c91b6d332cae@siemens.com> Date: Wed, 14 Feb 2018 14:38:53 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <7bd0cc56-0dba-6a04-767a-de4edcc3be1e@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: pvTj/DZ5Y0yp On 2018-02-14 14:29, Jan Kiszka wrote: > On 2018-02-14 14:10, Jan Kiszka wrote: >> On 2018-02-14 13:57, Alexander Smirnov wrote: >>> On 02/14/2018 03:41 PM, Jan Kiszka wrote: >>>> On 2018-02-14 12:33, Alexander Smirnov wrote: >>>>> On 02/13/2018 11:05 PM, Jan Kiszka wrote: >>>>>> Yeah, finally Yocto/OE-like usability: This ensures for many cases that >>>>>> changes to recipes lead to rebuilds of dependent recipes, including the >>>>>> final image. Some extra measures are needed so that those rebuilds work >>>>>> with clean dirs. >>>>>> >>>>>> And if the change detection should not work, e.g. changes to file:// >>>>>> resources are not detected, then a clean or cleanall task is now >>>>>> available and ensures a proper manual rebuild. >>>>>> >>>>>> This massively increases the fun factor when developing Isar projects. >>>>> >>>>> >>>>> Wow, just noticed that with this series bitbake has started to run tasks >>>>> in parallel.. How it's working? :-) >>>>> >>>>> >>>>> Currently  4 running tasks (54 of 217)  24% >>>>> |######################################## >>>>>                       | >>>>> 0: mc:rpi-jessie:buildchroot-1.0-r0 do_build - 101s (pid 3271) >>>>> 1: mc:qemui386-stretch:buildchroot-1.0-r0 do_build - 101s (pid 3336) >>>>> 2: mc:qemui386-jessie:buildchroot-1.0-r0 do_build - 100s (pid 3457) >>>>> 3: mc:qemuarm-wheezy:buildchroot-1.0-r0 do_build - 100s (pid 3524) >>>> >>>> Didn't notice that this wasn't the case before (most of my workload had >>>> linear ordering), but I could imagine that the lacking signatures forced >>>> bitbake to serialize. Just guessing. >>>> >>> >>> There is still the same build problem as reported yesterday, log is >>> attached. Dropping patch #3 fixes it. >>> >>> Line I used to build: >>> >>> $ time bitbake multiconfig:qemuarm-wheezy:isar-image-base >>> multiconfig:qemuarm-jessie:isar-image-base >>> multiconfig:qemuarm-stretch:isar-image-base >>> multiconfig:qemui386-jessie:isar-image-base >>> multiconfig:qemui386-stretch:isar-image-base >>> multiconfig:qemuamd64-jessie:isar-image-base >>> multiconfig:qemuamd64-stretch:isar-image-base >>> multiconfig:rpi-jessie:isar-image-base >>> >>> Just for sure stated build in CI server: >>> http://isar-build.org:8080/job/isar_asmirnov_devel/8/console >>> >>> Also failed. Could I dropped this patch from the series? >> >> Not before you can explain why things fail and why that patch causes >> this. We need to understand the problem. Let me reproduce... > > Yeah, I get some bug as well, but a different & well-known one: > > dpkg: error: dpkg status database is locked by another process > > So, I'm afraid we will find more of these sporadic breakage, now that > parallelization works better.... BTW, I'm testing with https://github.com/siemens/isar/commits/jan/staging, i.e. the sum of all my misdoing. Good news is that I just reproduced your issue, now digging into what corrupts the isar-apt repo /wrt libhello-dev. Bad news: I had to restart 5 times due to the contention bug above. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux