From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: <isar-users@googlegroups.com>
Subject: Re: weird CI errors
Date: Wed, 13 Feb 2019 11:07:17 +0100 [thread overview]
Message-ID: <20190213110717.2182406f@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190213083820.GO805@yssyq.m.ilbers.de>
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
>
> With kind regards,
> Baurzhan.
>
prev parent reply other threads:[~2019-02-13 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:12 Henning Schild
2019-02-13 8:38 ` Baurzhan Ismagulov
2019-02-13 10:07 ` 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=20190213110717.2182406f@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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