On 7 November 2017 at 08:44, Dragos Iorgulescu <Dragos.Iorgulescu@enea.com> wrote:
Hi again!

I've managed to reproduce this by hand, by trying to clone the same repos as root, on the same host.
It seems that the use of "--depth=1" makes the command fail. When --depth is not used, the clone works correctly:

https://lists.linaro.org/pipermail/lava-announce/2017-September/000038.html
c6e06463 LAVA-998 - Default to shallow clones in overlay

https://projects.linaro.org/browse/LAVA-998

That could lead you to: https://review.linaro.org/#/c/21060/5/doc/v2/test-repositories.rst

That leads to here: https://staging.validation.linaro.org/static/docs/v2/test-repositories.html#shallow-clones-in-git

That includes an example of how to request not to use shallow clones for specific repositories.

However, you should check why this repository cannot be used as a shallow clone - it may be that the repository itself has errors in git which need to be fixed up.

 

root@eltf-qemu01:~/tmp_lava# git clone git://git.enea.se/eltf/lava.git /var/lib/lava/dispatcher/tmp/384/lava-overlay-SXDmxh/lava-384/0/tests/0_healthcheck-runner --depth=1
Cloning into '/var/lib/lava/dispatcher/tmp/384/lava-overlay-SXDmxh/lava-384/0/tests/0_healthcheck-runner'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
 
root@eltf-qemu01:~/tmp_lava# git clone git://git.enea.se/eltf/lava.git /var/lib/lava/dispatcher/tmp/384/lava-overlay-SXDmxh/lava-384/0/tests/0_healthcheck-runner
Cloning into '/var/lib/lava/dispatcher/tmp/384/lava-overlay-SXDmxh/lava-384/0/tests/0_healthcheck-runner'...
remote: Counting objects: 1253, done.
remote: Compressing objects: 100% (1241/1241), done.
remote: Total 1253 (delta 675), reused 0 (delta 0)
Receiving objects: 100% (1253/1253), 239.59 KiB | 0 bytes/s, done.
Resolving deltas: 100% (675/675), done.
Checking connectivity... done.

Is there a way to avoid the use of the --depth parameter (i.e. a setting), or should I just make the changes in the LAVA code?

Just because LAVA is open source does not mean you should modify the code every time. Please read the documentation.
 

Thanks again!
-- 
/Dragoş
 

On 2017-11-06 11:30:35+02:00 Dragos Iorgulescu wrote:

Hi!

Just upgraded from 2017.6 to 2017.10-1. 
Tried re-running some jobs that worked fine just before the upgrade and noticed that git checkouts can no longer pe performed.

The encountered error is:
fatal: The remote end hung up unexpectedly\nfatal: early EOF\nfatal: index-pack failed\n

Tried checking out manualy on the host, using the same repo. It works.

How could I proceed investigating this? 
Could this be related to some lava user configuration that got reset (I don't know if git-related configs are associated with LAVA)?

Thanks in advance (again)!
P.S: I have attached the plain job log
-- 
/Dragoş

_______________________________________________
Lava-users mailing list
Lava-users@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lava-users




--

Neil Williams
=============
neil.williams@linaro.org
http://www.linux.codehelp.co.uk/