Misleading start time reported in statistics

Bug #1418543 reported by Phill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned
duplicity (Ubuntu)
New
Undecided
Unassigned

Bug Description

The statistics section reports a start and end time, however, the start time on my machine is always over 5 minutes after the actual start time. The section below shows a log file from a script that logs the current time, immediately runs duplicity and then logs the end time. During the 5+ minutes not included in the statistics the CPU usage by duplicity (as shown by `top`) is extremely high.

--

Backup Started Thu Feb 5 09:00:01 UTC 2015
Import of duplicity.backends.giobackend Failed: No module named gio
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Jan 29 16:00:04 2015
--------------[ Backup Statistics ]--------------
StartTime 1423127161.48 (Thu Feb 5 09:06:01 2015)
EndTime 1423127165.40 (Thu Feb 5 09:06:05 2015)
ElapsedTime 3.92 (3.92 seconds)
SourceFiles 799
SourceFileSize 514518209 (491 MB)
NewFiles 0
NewFileSize 0 (0 bytes)
DeletedFiles 0
ChangedFiles 1
ChangedFileSize 1966187 (1.88 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 1
RawDeltaSize 14530 (14.2 KB)
TotalDestinationSizeChange 1467 (1.43 KB)
Errors 9
-------------------------------------------------

Backup Ended Thu Feb 5 09:06:06 UTC 2015

---

Package: duplicity
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 1028
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 0.6.18-0ubuntu3.5
Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python2.7, python (>= 2.7.1-0ubuntu2), python (<< 2.8), python-gnupginterface (>= 0.3.2-9.1), python-lockfile
Suggests: python-boto, ncftp, rsync, ssh, python-paramiko
Breaks: deja-dup (<< 22.0-0ubuntu5)
Description: encrypted bandwidth-efficient backup
 Duplicity backs directories by producing encrypted tar-format volumes
 and uploading them to a remote or local file server. Because duplicity
 uses librsync, the incremental archives are space efficient and only
 record the parts of files that have changed since the last backup.
 Because duplicity uses GnuPG to encrypt and/or sign these archives, they
 will be safe from spying and/or modification by the server.
Homepage: http://duplicity.nongnu.org/
Original-Maintainer: Alexander Zangerl <email address hidden>

Phill (phill.l)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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