make check fails on Arch Linux

Bug #917057 reported by Justin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned
Arch Linux
New
Undecided
Unassigned

Bug Description

I simply run make check, using duplicity-0.6.17. This is on a gentoo linux 64 bit system.

make[2]: Entering directory `/mnt/tmpfs/deja-dup-21.4/tests/common'
/bin/sh ../../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -I../../common -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng15 -O2 -pipe -ftracer -march=corei7-avx -mtune=corei7-avx -mcx16 -msahf -mno-movbe -maes -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm -mavx -msse4.2 -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -frecord-gcc-switches -g -Wimplicit-function-declaration -Wl,-O1 -Wl,--as-needed -Wl,-O1 -Wl,--hash-style=gnu -Wl,--sort-common -o common common-common.o -pthread -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 ../../common/libcommon.la
libtool: link: x86_64-pc-linux-gnu-gcc -I../../common -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng15 -O2 -pipe -ftracer -march=corei7-avx -mtune=corei7-avx -mcx16 -msahf -mno-movbe -maes -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm -mavx -msse4.2 -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -frecord-gcc-switches -g -Wimplicit-function-declaration -Wl,-O1 -Wl,--as-needed -Wl,-O1 -Wl,--hash-style=gnu -Wl,--sort-common -o common common-common.o -pthread -lnotify -lgdk_pixbuf-2.0 ../../common/.libs/libcommon.a -lgio-2.0 -lgobject-2.0 -lgthread-2.0 -lgnome-keyring -lgmodule-2.0 -lrt -lglib-2.0 -pthread
dbus-launch ./common
/unit/utils/testing_mode: OK
/unit/utils/get_day: OK
/unit/utils/parse_dir: OK
/unit/utils/parse_dir_list: OK
/unit/operation/mode_to_string: OK
/backup/bad_volume: ** (./common:20667): DEBUG: DuplicityInstance.vala:196: Running the following duplicity (20696) command: duplicity 'collection-status' '--exclude=/tmp/not/a/thing' '--exclude=/local/home/justin/.local/share/Trash' '--exclude=/local/home/justin/.xsession-errors' '--exclude=/local/home/justin/.thumbnails' '--exclude=/local/home/justin/.gvfs' '--exclude=/local/home/justin/.adobe/Flash_Player/AssetCache' '--include=/local/home/justin' '--exclude=/local/home/justin' '--exclude=/sys' '--exclude=/proc' '--exclude=/tmp' '--exclude=/tmp/deja-dup-test-4S3xzh/cache/deja-dup' '--exclude=/tmp/deja-dup-test-4S3xzh/cache' '--exclude=**' '--gio' 'file:///tmp/not/a/thing' '--no-encryption' '--verbosity=9' '--gpg-options=--no-use-agent' '--archive-dir=/tmp/deja-dup-test-4S3xzh/cache/deja-dup' '--log-fd=12'

** (./common:20667): DEBUG: DuplicityInstance.vala:568: duplicity (20696) exited with value 255

** WARNING **: common.vala:217: Cancel didn't match; expected 0, got 1

Revision history for this message
Feanor (michael.pusterhofer) wrote :

Could reproduce a similar behaviour in arch64 - duplicity 0.6.17-3

/backup/bad_volume: ** (./common:4926): DEBUG: DuplicityInstance.vala:196: Running the following duplicity (4951) command: duplicity 'collection-status' '--exclude=/tmp/not/a/thing' '--exclude=/home/michael/.local/share/Trash' '--exclude=/home/michael/.xsession-errors' '--exclude=/home/michael/.thumbnails' '--exclude=/home/michael/.gvfs' '--exclude=/home/michael/.adobe/Flash_Player/AssetCache' '--include=/home/michael' '--exclude=/sys' '--exclude=/proc' '--exclude=/tmp' '--exclude=/tmp/deja-dup-test-CIE0FI/cache/deja-dup' '--exclude=/tmp/deja-dup-test-CIE0FI/cache' '--exclude=**' '--gio' 'file:///tmp/not/a/thing' '--no-encryption' '--verbosity=9' '--gpg-options=--no-use-agent' '--archive-dir=/tmp/deja-dup-test-CIE0FI/cache/deja-dup' '--log-fd=12'

** (./common:4926): DEBUG: DuplicityInstance.vala:568: duplicity (4951) exited with value 1

** (./common:4926): DEBUG: DuplicityInstance.vala:196: Running the following duplicity (4955) command: duplicity 'collection-status' '--exclude=/tmp/not/a/thing' '--exclude=/home/michael/.local/share/Trash' '--exclude=/home/michael/.xsession-errors' '--exclude=/home/michael/.thumbnails' '--exclude=/home/michael/.gvfs' '--exclude=/home/michael/.adobe/Flash_Player/AssetCache' '--include=/home/michael' '--exclude=/sys' '--exclude=/proc' '--exclude=/tmp' '--exclude=/tmp/deja-dup-test-CIE0FI/cache/deja-dup' '--exclude=/tmp/deja-dup-test-CIE0FI/cache' '--exclude=**' '--gio' 'file:///tmp/not/a/thing' '--no-encryption' '--verbosity=9' '--gpg-options=--no-use-agent' '--archive-dir=/tmp/deja-dup-test-CIE0FI/cache/deja-dup' '--log-fd=19'

** (./common:4926): DEBUG: DuplicityInstance.vala:568: duplicity (4955) exited with value 1

** WARNING **: common.vala:226: Error string didn't match; expected Blarg blarg do something, got Failed with an unknown error.

Revision history for this message
Justin (jlec) wrote :

Same on gentoo

dbus-launch ./common
/unit/utils/testing_mode: OK
/unit/utils/get_day: OK
/unit/utils/parse_dir: OK
/unit/utils/parse_dir_list: OK
/unit/operation/mode_to_string: OK
/backup/bad_volume: ** (./common:18111): DEBUG: DuplicityInstance.vala:196: Running the following duplicity (18148) command: duplicity 'collection-status' '--exclude=/tmp/not/a/thing' '--exclude=/var/tmp/portage/app-backup/deja-dup-21.4/temp/.gvfs' '--include=/var/tmp/portage/app-backup/deja-dup-21.4/temp' '--exclude=/sys' '--exclude=/proc' '--exclude=/var/tmp/portage/app-backup/deja-dup-21.4/temp' '--exclude=/tmp/deja-dup-test-oXAl84/cache/deja-dup' '--exclude=/tmp/deja-dup-test-oXAl84/cache' '--exclude=**' '--gio' 'file:///tmp/not/a/thing' '--no-encryption' '--verbosity=9' '--gpg-options=--no-use-agent' '--archive-dir=/tmp/deja-dup-test-oXAl84/cache/deja-dup' '--log-fd=12'

** (./common:18111): DEBUG: DuplicityInstance.vala:568: duplicity (18148) exited with value 255

** WARNING **: common.vala:217: Cancel didn't match; expected 0, got 1
make[2]: *** [check] Trace/breakpoint trap
make[2]: Leaving directory `/var/tmp/portage/app-backup/deja-dup-21.4/work/deja-dup-21.4/tests/common'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-backup/deja-dup-21.4/work/deja-dup-21.4/tests'
make: *** [check-recursive] Error 1

Michael Terry (mterry)
summary: - deja-dup-21.4 fails test - common.vala:217: Cancel didn't match;
- expected 0, got 1
+ make check fails on Arch Linux
Changed in deja-dup:
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

Alright, I know what part of this is. On Arch Linux, /usr/bin/python is a symlink to python3. On most other Linuxes I've seen, it's been a symlink to a version of python2.

This causes the mock duplicity script used in the tests to fail (written for python2, but is run under python3). I can workaround this by just porting the script to python3 (a good thing to do anyway). Then I hit another error, which I'm looking into.

Revision history for this message
Justin (jlec) wrote :

I don't think this is the issue. On my system the situation is that /usr/bin/python calls python in API version 2 not 3.

Xytime (xytime)
no longer affects: gentoo
Revision history for this message
Michael Terry (mterry) wrote :

I'm going to tentatively mark this fix released. It's been a while and as far as I can tell, trunk and recent releases pass tests. Please reopen if you find differently. Thanks!

Changed in deja-dup:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.