From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/2] test rebuilding hello series
Date: Mon, 25 Feb 2019 19:28:30 +0100 [thread overview]
Message-ID: <20190225192830.25226f0c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <211ff065-dd24-ab68-cd87-75e8c32e8290@ilbers.de>
Am Wed, 20 Feb 2019 16:53:15 +0300
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Hi Henning,
>
> I just rebased your series for convenience.
>
> Your last email on this topic was on Wed, 13 Feb (see below)
>
> Any progress on that?
>
> As I said the problem is reproduced on my local PC - so this is
> not jenkins environment problem.
I can reproduce it ... kind of. Because it is not always the same
error. I might just smuggle in the "hello" where the ssh key package is
at the moment, and forget about the fact that the example images should
maybe not contain these packages.
Henning
> Maxim.
>
> -------- Forwarded Message --------
> Subject: Re: weird CI errors
> Date: Wed, 13 Feb 2019 11:07:17 +0100
> From: Henning Schild <henning.schild@siemens.com>
> To: Baurzhan Ismagulov <ibr@radix50.net>
> CC: isar-users@googlegroups.com
>
> On Wed, 13 Feb 2019 09:38:20 +0100
> Baurzhan Ismagulov <ibr@radix50.net> wrote:
>
> > On Tue, Feb 12, 2019 at 07:12:16PM +0100, Henning Schild wrote:
> > > Turns out the CI runs into some weird issue that i can not
> > > reproduce on my machine. From a first couple of google hits it
> > > might have to do with network filesystem backing storage, might
> > > that be the case?
> >
> > The drive is local, no network fs.
> >
> >
> > > Error message:
> > > | shell-init: error retrieving current directory: getcwd: cannot
> > > access parent directories: Value too large for defined data
> > > type
> >
> > Which task? Google also shows that the directory might have been
> > deleted. Can we rule out races?
>
> Might be a race, my local setup does not do parrallel multiconfig. I
> think it was ${S} of the recipe hello. I do not see why any other task
> would go ahead and remove/recreate that, but maybe some false sharing
> between multiconfigs.
>
> I will try if i can reproduce the issue by running the whole ci job.
> At least on the jenkins it seem pretty reproducable.
>
> Henning
>
>
> On 2/19/19 4:20 PM, Henning Schild wrote:
> > Hi Maxim,
> >
> > why did you rebase and post that? Are you looking into the issue it
> > seems to reveal but not cause?
> >
> > Henning
> >
> > On Tue, 19 Feb 2019 07:37:34 +0100
> > "Maxim Yu. Osipov" <mosipov@ilbers.de> wrote:
> >
> >> Hello,
> >>
> >> This is a rebased v1 against current 'next'.
> >>
> >> Fails on 'scripts/ci_build.sh -q'.
> >>
> >> Regards,
> >> Maxim.
> >>
> >> Henning Schild (2):
> >> ci: test rebuilding "hello"
> >> ci: move IMAGE_INSTALL from config to ci script
> >>
> >> meta-isar/conf/multiconfig/qemuamd64-buster.conf | 2 --
> >> scripts/ci_build.sh | 8 ++++++++
> >> 2 files changed, 8 insertions(+), 2 deletions(-)
> >>
> >
>
>
prev parent reply other threads:[~2019-02-25 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 6:37 Maxim Yu. Osipov
2019-02-19 6:37 ` [PATCH v2 1/2] ci: test rebuilding "hello" Maxim Yu. Osipov
2019-02-19 6:37 ` [PATCH v2 2/2] ci: move IMAGE_INSTALL from config to ci script Maxim Yu. Osipov
2019-02-19 15:20 ` [PATCH v2 0/2] test rebuilding hello series Henning Schild
2019-02-20 13:53 ` Maxim Yu. Osipov
2019-02-25 18:28 ` Henning Schild [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190225192830.25226f0c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox