weird CI errors

weird CI errors

[Henning Schild]

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

Re: weird CI errors

[Baurzhan Ismagulov]

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.

Re: weird CI errors

[Henning Schild]

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.
>