Bug#674834: FTBFS: test convert5to6 fails on FS w/o nanosecond resolution

[Lars Wirzenius]

On Mon, May 28, 2012 at 06:28:40AM +0200, Sven Hartge wrote:
 This took some time for me to debug since I first thought this was
 cowbuilders fault, but by comparing my build system to a different one
 I discovered the lack of support for nanosecond timestamps because it
 still uses ext3.

Thanks for reporting this. I already have code to deal with
this when the backup/restore happens over sftp, so I'll change things
so that happens when using filesystems that don't have reasonable time
stamps. I'll fix this for the next upload.

-- 
All my predictions will turn out to be false


signature.asc
Description: Digital signature

Bug#674834: FTBFS: test convert5to6 fails on FS w/o nanosecond resolution

[Sven Hartge]

Package: obnam
Version: 0.26-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi Lars,

during a rebuild of obnam I discovered the following error:

on a filesystem without nanosecond resolution the convert5to6 test
fails:

---8--

FAIL: convert5to6: stdout diff:  
--- /dev/null   2009-03-24 13:37:39.0 +
+++ tests/convert5to6.stdout-actual 2012-05-28 04:13:25.0 +
@@ -0,0 +1,41 @@
+--- data.summain   2012-05-06 16:43:10.0 +
 restored.summain   2012-05-28 04:13:25.0 +
+@@ -1,33 +1,33 @@
+ Name: data
+-Mtime: 2012-04-29 18:45:44.050349637 +
++Mtime: 2012-04-29 18:45:44.0 +
+ Mode: 40775
+ Ino: 1
+ Dev: 1
+ Nlink: 3
+ 
+ Name: data/0
+-Mtime: 2012-04-29 18:45:44.050349637 +
++Mtime: 2012-04-29 18:45:44.0 +
+ Mode: 40775
+ Ino: 2
+ Dev: 1
+ Nlink: 3
+ 
+ Name: data/0/0
+-Mtime: 2012-04-29 18:45:44.050349637 +
++Mtime: 2012-04-29 18:45:44.0 +
+ Mode: 40775
+ Ino: 3
+ Dev: 1
+ Nlink: 3
+ 
+ Name: data/0/0/0
+-Mtime: 2012-04-29 18:45:44.050349637 +
++Mtime: 2012-04-29 18:45:44.0 +
+ Mode: 40775
+ Ino: 4
+ Dev: 1
+ Nlink: 2
+ 
+ Name: data/0/0/0/0
+-Mtime: 2012-04-29 18:45:44.050349637 +
++Mtime: 2012-04-29 18:45:44.0 +
+ Mode: 100664
+ Ino: 5
+ Dev: 1

FAIL: convert5to6: got exit code 1, expected 0

---8--

This took some time for me to debug since I first thought this was
cowbuilders fault, but by comparing my build system to a different one
I discovered the lack of support for nanosecond timestamps because it
still uses ext3.

Recompiling obnam on a newer system with ext4 allows the build to succeed
(after working around #674832).

After looking through the build logs it is apparent most buildds don't support
nanosecond timestamps either.

Grüße,
Sven.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'experimental'), (400, 'testing'), (300, 
'stable')
Architecture: i386 (x86_64)

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages obnam depends on:
ii  libc6 2.13-32
ii  python2.7.2-10
ii  python-cliapp 0.29-1
ii  python-larch  1.20120527-1
ii  python-paramiko   1.7.7.1-2
ii  python-tracing0.6-2
ii  python-ttystatus  0.18-1
ii  python2.6 2.6.7-4
ii  python2.7 2.7.3~rc2-2.1

obnam recommends no packages.

obnam suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org