From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6521316140522668032 X-Received: by 10.25.163.211 with SMTP id m202mr622474lfe.23.1518362234730; Sun, 11 Feb 2018 07:17:14 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.65.133 with SMTP id d5ls1059263ljf.11.gmail; Sun, 11 Feb 2018 07:17:13 -0800 (PST) X-Google-Smtp-Source: AH8x224YVD76Npg/g0oe+FkwUP848p/TyK79lO7l8gIPlLEsTULE7IJToc6ULUmBCG+mnd/+GvCQ X-Received: by 10.46.69.138 with SMTP id s132mr551316lja.44.1518362233816; Sun, 11 Feb 2018 07:17:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518362233; cv=none; d=google.com; s=arc-20160816; b=G+2Pk5CI6303s8XuXJ67ixDRLVv9LrVqqDq7DZImjZyyCzxtotHICZnwqg1s7BCtYo P6SbIB0CS1wFVYGpF19+fjga9U8uXeXTK7Y6Gj8Gw+97rWALlKU8iNm5sP0OYsoKXpmk ZzMBE3Cp8TO33ER6kd3t5FdC0sB7BGehiZvy7acDDjOAekEdiDXVo6RGgfXe+L3AM+n2 QMGUz/buJlDCU6LXHttRonrK0XHYcXSnElo0ORwBXpOw4PjiNiAomBd7r41ikAQABkry WuF6tNccJeSPdAm4ZLyRIDyUQRioyvPtdNNrdmDGGGuoOta5d19in6dDvUPW5OXEa0OA po7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:mime-version:user-agent :date:message-id:subject:from:to:arc-authentication-results; bh=enb7iCmSirk38McWOVqYJYYU9Zi1JGJ68cgde5PkeAY=; b=NfcPj8teJY08JH3DzLxMSXNqIQQiKYspdD9L838UrtSFMS7Ry6gR7W6qlUYZRsk6oI 3kqWhGCYj0BjwVp98fN7fL4gZzf4viXbe2Mjq6i1K8cHzg4KNQ5SEw/rsR7e3ATv1Qi9 JiWoimdBJjHH0rgnXXClrYLm5MGaJuHE8kSpsd08eGrLLj4+hFNec4elcoNxSJLpg5IT 9X7ZNlPQqEBCDmyRtTJ56c/cZs3tAfn7q8VbrWwFyq0Uwu6ACvAubEezxF1eRkDJt8WK M/tD/UwuXcNGi/ZThibYFSPhOhBinB22oHMVoQJp8Ww8L/0Wak43fMeUjVInu5Bb2G8h ihBw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id z11si392359lff.1.2018.02.11.07.17.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Feb 2018 07:17:13 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w1BFHD30001476 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 11 Feb 2018 16:17:13 +0100 Received: from [167.87.32.7] ([167.87.32.7]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w1BFHCcV009971 for ; Sun, 11 Feb 2018 16:17:12 +0100 X-Mozilla-News-Host: news://news.gmane.org:119 To: isar-users From: Jan Kiszka Subject: Build can sporadically fail due to dpkg contention in buildchroot Message-ID: <79bd216e-53ca-5485-4f6c-66050d08ed5f@siemens.com> Date: Sun, 11 Feb 2018 16:17:12 +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 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: RC69p9wJFnh9 Hi all, I got this failure of example-hello:do_build already twice while doing rebuild tests with my kernel series (ie. with more independent buildchroot users): DEBUG: Executing shell function do_build Get:1 file:/isar-apt isar InRelease Ign:1 file:/isar-apt isar InRelease Get:2 file:/isar-apt isar Release [2,864 B] Get:2 file:/isar-apt isar Release [2,864 B] Get:3 file:/isar-apt isar Release.gpg Ign:3 file:/isar-apt isar Release.gpg Get:4 file:/isar-apt isar/main amd64 Packages [1,135 B] Reading package lists... W: The repository 'file:/isar-apt isar Release' is not signed. hostname: No address associated with hostname dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_install: Compatibility levels before 9 are deprecated (level 7 in use) dh_installdocs dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use) dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use) dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'hello-build-deps' in '../hello-build-deps_0.2_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! dpkg: error: dpkg status database is locked by another process mk-build-deps: dpkg --unpack failed [...] So we have a concurrency problem when building over the same dpkg database. Looks like we need to synchronize (lock-protect) the access to it, which also means pulling out the dependency installation from the regular build step. Is that feasible at all? Any alternatives (besides retrying such builds...)? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux