* weird CI errors
@ 2019-02-12 18:12 Henning Schild
2019-02-13 8:38 ` Baurzhan Ismagulov
0 siblings, 1 reply; 3+ messages in thread
From: Henning Schild @ 2019-02-12 18:12 UTC (permalink / raw)
To: isar-users
Hi,
i pushed a few trivial commits to a staging branch to CI them before
sending them.
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?
Error message:
| shell-init: error retrieving current directory: getcwd: cannot access
parent directories: Value too large for defined data type
Found in http://isar-build.org:8080/job/isar_henning_ilbers-ci/77
Henning
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: weird CI errors
2019-02-12 18:12 weird CI errors Henning Schild
@ 2019-02-13 8:38 ` Baurzhan Ismagulov
2019-02-13 10:07 ` Henning Schild
0 siblings, 1 reply; 3+ messages in thread
From: Baurzhan Ismagulov @ 2019-02-13 8:38 UTC (permalink / raw)
To: isar-users
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?
With kind regards,
Baurzhan.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: weird CI errors
2019-02-13 8:38 ` Baurzhan Ismagulov
@ 2019-02-13 10:07 ` Henning Schild
0 siblings, 0 replies; 3+ messages in thread
From: Henning Schild @ 2019-02-13 10:07 UTC (permalink / raw)
To: Baurzhan Ismagulov; +Cc: isar-users
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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-02-13 10:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-12 18:12 weird CI errors Henning Schild
2019-02-13 8:38 ` Baurzhan Ismagulov
2019-02-13 10:07 ` Henning Schild
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox