Ivo De Decker <iv...@debian.org> writes: > The failure that happens on the i386 buildd is this one: > > 1) Failure: > clone::nonetwork::local_absolute_path > [/«PKGBUILDDIR»/tests/clone/nonetwork.c:91] > Function call failed: (git_clone(&g_repo, local_src, "./foo", &g_options)) > error -1 - git_path_direach callback returned -1 > > > I can reproduce this in my test environment on i386 and amd64. It only happens > when the builddir and /tmp are on different filesystems. It seems the local > clone tries to create a hard link, which fails across filesystems (the fact > that this happens without fallback is an error in itself, so the test actually > discovered a problem here). When setting the TMPDIR to a directory on the same > filesystem, the test doesn't hit this issue, and the build works fine.
I've had a go at reproducing this locally, but it seems to be a pretty subtle bug. My TMP_DIR on one of my machines is on a different file system to my builddir but it seems to switch to copying instead of linking during the clone. I can see this with strace. They do stat /tmp and . before beginning the copy/link. I realise it's probably futile but could you please run stat and compare your device id's. That is how they are checking that they are the same FS in the clone code. -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
