"make check" fails with "rsync: get_xattr_names: llistxattr(""[source root]/t/sampledata/var/b"",1024) failed: No such file or directory (2)"

[Karl-Philipp Richter]

Hi,

git clean -x -f -d
./configure
make
make check

fails with

if test -e t/tmp/test-log; then rm -r t/tmp/test-log; fi
mkdir -p t/tmp/test-log
./wvtest watch --no-counts make runtests-python runtests-cmdline
Testing "all" in make runtests-python runtests-cmdline:

! Startup: . 0.110s ok
! t/test-restore-single-file.sh all: ........... 0.425s ok
! lib/bup/t/tbloom.py test_bloom: ......... 0.170s ok
! t/test-tz.sh half hour TZ: ... 0.026s ok
! t/test-drecurse.sh drecurse: ..... 0.105s ok
! t/test-compression.sh compression: ............ 1.038s ok
! t/test-rm-between-index-and-save.sh remove file: ....... 0.642s ok
! t/test-meta.sh meta --create/--extract: ... 0.194s ok
! t/test-sparse-files.sh sparse restore on cifs, assuming 16384B
blocks:
rsync error: some files/attrs were not transferred (see previous
errors) (code 23) at main.c(1183) [sender=3.1.1]
! t/test-fsck.sh:11 /mnt/richtercloud/sources/bup/t/sync-tree
/mnt/richtercloud/sources/bup/t/sampledata/
/mnt/richtercloud/sources/bup/t/tmp/test-fsck.sh-KduwFbW/src/ FAILED

called from t/test-fsck.sh:11 WVPASS
/mnt/richtercloud/sources/bup/t/sync-tree
/mnt/richtercloud/sources/bup/t/sampledata/
/mnt/richtercloud/sources/bup/t/tmp/test-fsck.sh-KduwFbW/src/
Makefile:175: recipe for target 'tmp-target-run-test-fsck.sh' failed
make[1]: *** [tmp-target-run-test-fsck.sh] Error 1
rsync: get_xattr_names:
llistxattr(""/mnt/richtercloud/sources/bup/t/sampledata/var/b"",1024)
failed: No such file or directory (2)
rsync: get_xattr_names:
llistxattr(""/mnt/richtercloud/sources/bup/t/sampledata/var/c"",1024)
failed: No such file or directory (2)
rsync: get_xattr_names:
llistxattr(""/mnt/richtercloud/sources/bup/t/sampledata/var/abs-symlink"",1024)
failed: No such file or directory (2)
IO error encountered -- skipping file deletion
rsync error: some files/attrs were not transferred (see previous
errors) (code 23) at main.c(1183) [sender=3.1.1]
! t/test-meta.sh:103 /mnt/richtercloud/sources/bup/t/sync-tree
/mnt/richtercloud/sources/bup/t/sampledata/
/mnt/richtercloud/sources/bup/t/tmp/test-meta.sh-uOR6han/src/ FAILED
Alarm timed out! No test results for too long.

called from t/test-meta.sh:103 WVPASS
/mnt/richtercloud/sources/bup/t/sync-tree
/mnt/richtercloud/sources/bup/t/sampledata/
/mnt/richtercloud/sources/bup/t/tmp/test-meta.sh-uOR6han/src/
called from t/test-meta.sh:136 WVPASS setup-test-tree
Makefile:175: recipe for target 'tmp-target-run-test-meta.sh' failed
make[1]: *** [tmp-target-run-test-meta.sh] Error 1

! Killed by signal FAILED
Makefile:184: recipe for target 'test' failed
make: *** [test] Error 125

experienced with 0.27-56-gd4c3c48

-Kalle

[Rob Browning]

Karl-Philipp Richter <ric...@richtercloud.de> writes:

> fails with
>
> if test -e t/tmp/test-log; then rm -r t/tmp/test-log; fi
> mkdir -p t/tmp/test-log
> ./wvtest watch --no-counts make runtests-python runtests-cmdline
> Testing "all" in make runtests-python runtests-cmdline:
>
> ! Startup: . 0.110s ok
> ! t/test-restore-single-file.sh all: ........... 0.425s ok
> ! lib/bup/t/tbloom.py test_bloom: ......... 0.170s ok
> ! t/test-tz.sh half hour TZ: ... 0.026s ok
> ! t/test-drecurse.sh drecurse: ..... 0.105s ok
> ! t/test-compression.sh compression: ............ 1.038s ok
> ! t/test-rm-between-index-and-save.sh remove file: ....... 0.642s ok
> ! t/test-meta.sh meta --create/--extract: ... 0.194s ok
> ! t/test-sparse-files.sh sparse restore on cifs, assuming 16384B
> blocks:
> rsync error: some files/attrs were not transferred (see previous
> errors) (code 23) at main.c(1183) [sender=3.1.1]

Possibly cifs related?

I just tested that commit (with the HAS_EXTENDED_CHECK fix) on FreeBSD
as root and it seemed fine.

Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

[Karl-Philipp Richter]

Am 27.12.2015 um 20:20 schrieb Rob Browning:
> Possibly cifs related?
Since it works on non-cifs mount and doesn't on cifs I'd say yes. Thanks
for the info. I don't know if `make check` is supposed to work on cifs,
but as long as it doesn't I'd suggest to make `make check` fail with a
verbose error message, like `(currently) 'make check' isn't supported on
cifs [(see ... for details)]`.

> I just tested that commit (with the HAS_EXTENDED_CHECK fix) on FreeBSD
> as root and it seemed fine.

If `root` is necessary I'd suggest a similar message for invocations of
`make check` as non-root.

-Kalle

[Rob Browning]

Karl-Philipp Richter <ric...@richtercloud.de> writes:

> Am 27.12.2015 um 20:20 schrieb Rob Browning:
>> Possibly cifs related?
> Since it works on non-cifs mount and doesn't on cifs I'd say yes. Thanks
> for the info. I don't know if `make check` is supposed to work on cifs,
> but as long as it doesn't I'd suggest to make `make check` fail with a
> verbose error message, like `(currently) 'make check' isn't supported on
> cifs [(see ... for details)]`.

It's not so much that it's not supported, just that we haven't tracked
down and fixed the problems we apparently have there.

> If `root` is necessary I'd suggest a similar message for invocations of
> `make check` as non-root.

I just meant that root was what I happened to test -- "make check" is
intended to work as root, non-root, and as non-root using fakeroot.