From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6767012587809800192 X-Received: by 2002:aca:3389:: with SMTP id z131mr11407418oiz.97.1575631103566; Fri, 06 Dec 2019 03:18:23 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:aca:784:: with SMTP id 126ls1215473oih.8.gmail; Fri, 06 Dec 2019 03:18:23 -0800 (PST) X-Google-Smtp-Source: APXvYqwT3PHEeO012DSRAoufXyK8IWZFyOeoOKRakFAYl8/tSSqDck5vVktosTdNJ5crBGPxLz2Y X-Received: by 2002:aca:ad11:: with SMTP id w17mr12040624oie.85.1575631103120; Fri, 06 Dec 2019 03:18:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575631103; cv=none; d=google.com; s=arc-20160816; b=xdOOAMG0+p3LISZ58iF1ykj0r33BuLhQpTkR1jDvyRTV49u5laqkn4V+8SFNdgH/09 BXFsVAn32uoMx0U+DB0LyX3UaTQ8aAN5PFrrbb2FFQ71Uzzmv1PQP0q1bqQ0kZaO4tJR Tgr7h5XaHFj8HvvlVe3//KdyQRrMzWhjHVKqDYOqnp7nfA8QexjAUXk05vUn9h8kqcl/ l+z/KHdgGVHJMBEjzY1cuQR5Xg0YiS1gnQ7iVQnrrfFvHLKnbD/MUGpBwqKLfCTFn4IN Axr7wn6SmyPFyOkIP94jWWtQNmc35fvvJjuiFEA4Ldj4bJ1K8HoKl4P4EUwPlifEKNab Z3eA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=v54CkrMxSNmw0yd+LTif8DSe1OKYuOhrK1FB7MfRtN4=; b=KI2oNyK5wrRxeuLaKMsIu0+40OGAIWvtx56n7LimOGKZiSUQC431X0nUnETiOS8UFM qCzTxJ4eAWyykko+N2OXEeuXcuv0eB3au6BhzG/wOX9eUb4gd+ceI550Oq0H6tlw11Yu kd0JXyEq31K0xWv12PzWbwTOkDB1iH56jx3NwtcuIilrXMng45UIfC/AxNNVX7pC/9d0 Q9OnF69cXXr54JxmpSbKTMsWzwOWKK+asl2LKRJ+KXTIwxa5PezH0rYmKtNX+HsZ/1Q6 W1NRXBrHTwf4SjCp/plBwJ4TuXl/gP82oAIBeMjZCg4328jOo5zcoJIeF5ehKAKP1Tsl UCtg== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pQLV1ybA; spf=pass (google.com: domain of vijaikumar.kanagarajan@gmail.com designates 2607:f8b0:4864:20::744 as permitted sender) smtp.mailfrom=vijaikumar.kanagarajan@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com. [2607:f8b0:4864:20::744]) by gmr-mx.google.com with ESMTPS id v14si710083otn.0.2019.12.06.03.18.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Dec 2019 03:18:23 -0800 (PST) Received-SPF: pass (google.com: domain of vijaikumar.kanagarajan@gmail.com designates 2607:f8b0:4864:20::744 as permitted sender) client-ip=2607:f8b0:4864:20::744; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pQLV1ybA; spf=pass (google.com: domain of vijaikumar.kanagarajan@gmail.com designates 2607:f8b0:4864:20::744 as permitted sender) smtp.mailfrom=vijaikumar.kanagarajan@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: by mail-qk1-x744.google.com with SMTP id x1so6114838qkl.12 for ; Fri, 06 Dec 2019 03:18:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v54CkrMxSNmw0yd+LTif8DSe1OKYuOhrK1FB7MfRtN4=; b=pQLV1ybA9zhqYVEx8ZHcwN0syU2UTA6dpAY+wF+WUI/Lzl+BEFS/Nj+hSomiMlDAuI A787O2D0CxOZekCv+h3qxp4Gi2rodjjcdAVb6QWaaGDg44fXJd2YjHqCTmwPPPxOrCfw Hctkjpvlx35iOK2IuIG4t/MysQfQ3MibTayX+YBz7oYFp0nErBsSg6tBAWiGlu3KjBUs XfUE3vX/kM+NiJWYKWMQhDe0OgAezpHJn3cyq5JUy1RY4iT0k0k2bg+qPztiElT1uutm HZbNJBFvgVyEmN9cBs/FwwxNuzlDFG9PyMf6f1nrvZGgGrCgJT6I8zrDzt1bXiR50qUM /1qA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v54CkrMxSNmw0yd+LTif8DSe1OKYuOhrK1FB7MfRtN4=; b=hMv17eqWyN32ppGq9DcTTFWmL+GpmJvVbCZpg3jGKnkB0jTjzkLbi7ukI6n4vMNofs A+0J40vKF/D2+lBuhjPwQYfU9JhjfdqTSAAY/R7dFocuQkTrL1D3XLoYCt+CI75Eubs4 eLQh4nvcgPPDRQHjEJijUlfDbP9iCJybe4FLVjFr+C4JSVJRVYL0H0iLGd2pl49jCQZ7 4a70IpCAqDfqzo/sZMS0OThxeMbv8UgNRx2N8fkjPeOseFDEqUF4Tp7tas4b0MGgZrtR 5gbTwx5yEWoeaVhcD8BCwr8UjIBAqJWrz+ADffMWK0f5PwHITTttVKzNRQgmyd+sRr06 tAOg== X-Gm-Message-State: APjAAAU9fxpaaRYRiUUwboC90ubvVI9q9K2Uj8ZqGD4hlHQSPtR6JahD zVY3cduEbekXfL0Rg5B7TTtYAFep0Tag8fvMEyQ= X-Received: by 2002:a37:4acc:: with SMTP id x195mr13036992qka.52.1575631102683; Fri, 06 Dec 2019 03:18:22 -0800 (PST) MIME-Version: 1.0 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> <86d0aa73-8927-dfda-5c5e-a795685e1461@siemens.com> In-Reply-To: <86d0aa73-8927-dfda-5c5e-a795685e1461@siemens.com> From: vijai kumar Date: Fri, 6 Dec 2019 16:48:10 +0530 Message-ID: Subject: Re: [PATCH] targz-img: Ignore tar exit code 1 To: Gylstorff Quirin Cc: Jan Kiszka , isar-users Content-Type: multipart/alternative; boundary="0000000000002c30e105990734dc" X-TUID: rs/Nz/7m/+dC --0000000000002c30e105990734dc Content-Type: text/plain; charset="UTF-8" Hi Quirin, Its a scratch build. Thanks, Vijai Kumar K On Fri 6 Dec, 2019, 4:43 PM Gylstorff Quirin, wrote: > > > 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 > --0000000000002c30e105990734dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Quirin,

I= ts a scratch build.

Than= ks,
Vijai Kumar K

On Fri 6 Dec, 2019, 4:43 PM G= ylstorff Quirin, <quirin= .gylstorff@siemens.com> wrote:


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 <Vijaikumar_Kanagara= jan@mentor.com>
>>>>
>>>> Sometimes during packaging tar prints a warning "file= changed as we read it"
>>>> and exits with return code 1. This is observed when we gen= erete 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 co= ndition.
>> But this is going to take a while.
>>
>> If it helps, the scenario is IMAGE_TYPE set to wic-img and targz-i= mg is
>> inherited so both are executed for a build. Also, on a seperate no= te
>
> 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/cl= asses/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.
=C2=A0From 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 multip= le image types.
>> I believe we could specify only one right now. Former is more clea= n and particularly
>> useful if one wants a wic for sd boot and tar for nfsroot. Plannin= g to take this up
>> next.
>
> Right, that is of general interest, indeed. Quirin has something plann= ed
> around the same use case as well.

>
> Jan
>
Quirin
--0000000000002c30e105990734dc--