From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6767012587809800192 X-Received: by 2002:adf:82f3:: with SMTP id 106mr15681187wrc.69.1575630835124; Fri, 06 Dec 2019 03:13:55 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:5284:: with SMTP id c4ls2383553wrv.15.gmail; Fri, 06 Dec 2019 03:13:54 -0800 (PST) X-Google-Smtp-Source: APXvYqzjuBcn8uiDZMInQK9PskqDdx7y5H7Lbm14qUsP8UuP7n3MK18bG/YooXvKc2ai8p4/yowl X-Received: by 2002:a05:6000:1047:: with SMTP id c7mr15781940wrx.341.1575630834566; Fri, 06 Dec 2019 03:13:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575630834; cv=none; d=google.com; s=arc-20160816; b=jcX1KCfh2maNxunJS+tNoA9FPBNvWQz2bkKbRUr85WgMM+mlkcEJb1eLwdjsWIU8h7 WTvbV+UT/SIrk9F6FPFx6anPWXW9IeBCoZy8UlHfwd2DO6gKJWi2sclBAyVrJxCd3wNY s6WIuLXkX1YyVs9EA6AW1ryuyVBnY4ODouPMXs5BXBKA8x2BdN1DfV+e0bFPecQXlU73 M15QTZZGrDlayY/97qXiQTFGeXSBOeoaihIC8/h89wBDUq4nObAY+d2oSKBJgQC3LZX7 R3TzHO7pM2xlsNrOGaoiONqpFmV+RExcTMVVCiX5OAyr+VePznEy09zj2cNnXMbFFp8N SyyA== 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:cc:to:subject; bh=pdIpSHfKyyMUgO0U5+VexmT5gAv45rQHjn5xFsrUz54=; b=sltUsE8rx1A1FoIOlebZDcx/iZ+nlFyQe/Myni/yEKBaHCKzG21TeiwnqAzp5iROwH I+11Sp75HVwc3QVlKmIdGWSH/bxlqESnCiXw0Seohxn7yu3t+OP7PA79lYSj371Q4kCa YQOyHHJv7RzTFfO6CeEap7gdspW98woJee3cuf6BrlTOJQtE04pTYv3QxN20BvS1/cZ5 ZZYXQi+rgpUrrZUWdzbpP02iNCuRMh+rpdXU7zGUAOa2LDiK7iHQgG33RnIoorScF8DZ 2AoEPdvXBXK9RCKC26WUibbjbACnpLyqog3Rf3GViKmOGIeUixCk2GJn8GrCvE06Gw9M 9ulg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of quirin.gylstorff@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=quirin.gylstorff@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id r11si707056wrl.3.2019.12.06.03.13.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Dec 2019 03:13:54 -0800 (PST) Received-SPF: pass (google.com: domain of quirin.gylstorff@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 quirin.gylstorff@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=quirin.gylstorff@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 thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id xB6BDrO1018010 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 6 Dec 2019 12:13:53 +0100 Received: from [139.25.69.120] ([139.25.69.120]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id xB6BDroZ020166; Fri, 6 Dec 2019 12:13:53 +0100 Subject: Re: [PATCH] targz-img: Ignore tar exit code 1 To: Jan Kiszka , Vijai Kumar K Cc: isar-users@googlegroups.com References: <20191205174441.16406-1-Vijaikumar_Kangarajan@mentor.com> <85e91f0a-da08-5345-a666-b3026bee4d96@siemens.com> <20191205191735.GA16912@oxygen> <7972e109-f8a0-6f21-bd00-4312610fd414@siemens.com> From: Gylstorff Quirin Message-ID: <86d0aa73-8927-dfda-5c5e-a795685e1461@siemens.com> Date: Fri, 6 Dec 2019 12:13:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <7972e109-f8a0-6f21-bd00-4312610fd414@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: QQyoIl6ElqHd On 12/5/19 8:31 PM, Jan Kiszka wrote: > On 05.12.19 20:17, Vijai Kumar K wrote: >> On Thu, Dec 05, 2019 at 07:04:07PM +0100, Jan Kiszka wrote: >>> On 05.12.19 18:44, vijaikumar.kanagarajan@gmail.com wrote: >>>> From: Vijai Kumar K >>>> >>>> Sometimes during packaging tar prints a warning "file changed as we read it" >>>> and exits with return code 1. This is observed when we generete both >>>> wic-img and targz-img together. Ignore the error. >>> >>> Ignoring errors is rarely a good idea. In this case, it tells you that >>> you have a bug in your layer that missing a dependency. I know this >>> because we once had the same issue in a product layer. So: NAK >>> >>> Jan >> >> Ah! Ok. Back to square one I guess. Its currently observed in our downstream setups >> only. I have no good reason to justify it. Reproducing this issue is gonna be difficult. >> Let me see if I can monitor file changes and pinpoint the exact condition. >> But this is going to take a while. >> >> If it helps, the scenario is IMAGE_TYPE set to wic-img and targz-img is >> inherited so both are executed for a build. Also, on a seperate note > > wic may have found a reason to modify the rootfs while integrating it. > So a first shot could be making targz depend on wic completion. > > BTW, this sounds similar to > https://gitlab.com/cip-project/cip-core/isar-cip-core/blob/next/classes/wic-targz-img.bbclass > - and that class may have the same issue... > In case of this class the wic is create first and tarball afterwards. From my expirence I never had the tarball creation failing during the cip or xenomai-builds which both use the targz class. Does the error during a clean build from scratch or only during a partial rebuild? >> IMAGE_TYPE's functionality could be extended to provide multiple image types. >> I believe we could specify only one right now. Former is more clean and particularly >> useful if one wants a wic for sd boot and tar for nfsroot. Planning to take this up >> next. > > Right, that is of general interest, indeed. Quirin has something planned > around the same use case as well. > > Jan > Quirin