Your message dated Sun, 10 Apr 2016 18:32:25 +0000
with message-id <[email protected]>
and subject line Not reproducible
has caused the Debian Bug report #790829,
regarding "Will now FTBFS with fresh cython 0.22.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
790829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790829
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bzr
Version: 2.6.0+bzr6602-2
Severity: important

I have just now uploaded fresh cython to sid and upon my testing bzr has
experienced problems (due to tests failing) while building with fresh
cython while build passed with the previous one, e.g.

======================================================================
FAIL: 
bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime(DirStateRevisionTree,WT4)
----------------------------------------------------------------------
Traceback (most recent call last):
_StringException: log: {{{
5154.196  creating repository in 
file:///tmp/testbzr-yhrYo1.tmp/bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime%28DirStateRevisionTree%2CWT4%29/work/tree/.bzr/.
5155.114  creating branch <bzrlib.branch.BzrBranchFormat7 object at 
0x7fd1e24a82d0> in 
file:///tmp/testbzr-yhrYo1.tmp/bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime%28DirStateRevisionTree%2CWT4%29/work/tree/
5156.501  trying to create missing lock 
'/tmp/testbzr-yhrYo1.tmp/bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime(DirStateRevisionTree,WT4)/work/tree/.bzr/checkout/dirstate'
5156.604  opening working tree 
'/tmp/testbzr-yhrYo1.tmp/bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime(DirStateRevisionTree,WT4)/work/tree'
5158.814  preparing to commit
    INFO  Committing to: 
/tmp/testbzr-yhrYo1.tmp/bzrlib.tests.per_tree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime(DirStateRevisionTree,WT4)/work/tree/
5158.932  Selecting files for commit with filter None
    INFO  added one
    INFO  Committed revision 1.
5160.836  Committed revid [email protected] 
as revno 1.
}}}

Traceback (most recent call last):
  File 
"/tmp/buildd/bzr-2.6.0+bzr6602/build/lib.linux-x86_64-2.7/bzrlib/tests/per_tree/test_get_file_mtime.py",
 line 44, in test_get_file_mtime
    'now: %f, mtime_file_id: %f' % (now, mtime_file_id ))
  File "/usr/lib/python2.7/unittest/case.py", line 424, in assertTrue
    raise self.failureException(msg)
AssertionError: now: 1435622024.948040, mtime_file_id: 1435622030.524000

which I don't know why triggered by cython (if it is).  Here you can find
a full build log:
http://www.onerussian.com/tmp/bzr_2.6.0+bzr6602-3_amd64.build

Cheers!

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bzr depends on:
ii  python-bzrlib  2.6.0+bzr6602-2
pn  python:any     <none>

Versions of packages bzr recommends:
ii  python-gpgme  0.3-1+b1

Versions of packages bzr suggests:
pn  bzr-doc              <none>
ii  bzrtools             2.6.0-2
pn  python-bzrlib.tests  <none>

-- debconf-show failed

--- End Message ---
--- Begin Message ---
I am going to optimistically close this bug report. cython in the
archive is now at 0.23, and many versions of bzr have built fine
against it.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to