From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6935390513328553984 X-Received: by 2002:a5d:4743:: with SMTP id o3mr13595378wrs.108.1614773122271; Wed, 03 Mar 2021 04:05:22 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:2e44:: with SMTP id u65ls1102219wmu.2.canary-gmail; Wed, 03 Mar 2021 04:05:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJwdCgnAG8inYTk0p6C1qLR3KqxWlQlSsL1YUjFwmayzgTsA72evWk8pX0r81gE58bbWTILM X-Received: by 2002:a1c:b789:: with SMTP id h131mr8938868wmf.106.1614773121257; Wed, 03 Mar 2021 04:05:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614773121; cv=none; d=google.com; s=arc-20160816; b=XePS+mKr6SQNMY6W+N8yvZS73TKBMdFWUxTFvRUKq+60iE8Q7pO4LtBW2BpLwHbTdm uSKh+hbDsjMgOBIWHalweVQakBRZCfsyy+SZaT+M8Pe3bq3FKGnb4JmiccMFMlq133Xq nk5ESCF2+bJO+lwVlssrGy095l0XpCQzNkXu0N+7ytXCnzGkfJK36Q7TGBioTs6ClnTY 2hhSILTX1EiPxnE3mDkZkYAPCA9+bELrOPDHgMW+tvTwtdzyJscpC7JwCVZDSxHm8Hyu uFNGBL4oEhX2YregVKuFSmYUwXAZoniMC9JmO04HHIMI1ta4pUMI9p+LCyHfj0nCSWCp CFtA== 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; bh=IA6hJcBQGkw5+cEOwSnlkJdNjg53hkBU5XSezL+UQGY=; b=nAXO3v2fcCVE3IC8X7hGLMFEFJNd2zJNxj6ltJr2ck9R9jmQhnbN4md2xPwfDP8EnS SsBB0mJBU9sG4IWjP23qq5gUH7/Egt/h83PHC/dEONzkLOf04wseiy+rg6511cyKuqPc sS9uD5GvrzTcZFGiXsA9exahLZfrKqtm/ItzniUMDValMXUzO7lAXaEEtqY+0srs/uD3 l3E3zOpOQQGWC5gYdmoG/zhvp/9OfdxUqnrboJCHN7OgVkkNp1irjUr/dh2S2aWg4QOz 205O9ibbNisC2TzSAm/wbkQatlsO/3ySrOCV4Rma/02k+DqiRm7cxtg1GtFhj/Fe+JpV kWOg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id h16si561092wrx.2.2021.03.03.04.05.21 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Mar 2021 04:05:21 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 123C5Kme011722 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Mar 2021 13:05:21 +0100 Received: from [139.22.114.127] ([139.22.114.127]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 123C5Kh6023625; Wed, 3 Mar 2021 13:05:20 +0100 Subject: Re: Custom recipe, multiple machines for same arch From: Jan Kiszka To: Daniel Machon , "isar-users@googlegroups.com" References: <2a8fcac4-d6c1-637b-a1e1-54a8e1dbabd4@siemens.com> Message-ID: Date: Wed, 3 Mar 2021 13:05:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <2a8fcac4-d6c1-637b-a1e1-54a8e1dbabd4@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: VuPVi2dACDPT On 03.03.21 13:04, Jan Kiszka wrote: > On 03.03.21 12:37, Daniel Machon wrote: >> Hi, >> >>   >> >> Is there an elegant way to handle custom recipes, that are used in >> multiple machines that target the same architecture. >> >> Currently when I try to execute a multi-machine build, it fails with: >> */Detect multiple executions of ../* >> >> You can get around this by changing PN = /recipe-name/-${MACHINE} in >> each custom recipe and IMAGE_INSTALL += /recipe-name/-${MACHINE} >> >> I am just wondering whether this is the best solution, or if there are >> any alternatives? >> > > Yes, you can share recipes across multiple configuration (multi-config). > You will find examples of that in Isar itself and also in [1]. > > But this can easily cause false-sharing problems. To detect those, we > installed an instrumentation that reported such a case in your setup. It > basically detects if there are variables evaluated by the recipe that > vary across the builds for different multi-config targets. > > The next thing then is to understand what makes the recipes specific to > the machines and then resolve that. One way is building the recipes > machine-specific, this is what you described above. But maybe there is > also a more elegant way in your case. This is hard to answer generally, > though. You may try to compare the task signatures of the different runs > via bitbake-diffsigs which should visualize the varying vars. > > Jan > [1] https://github.com/siemens/jailhouse-images