Your message dated Mon, 23 Jan 2017 00:13:36 +0100 (CET)
with message-id <[email protected]>
and subject line Re: swift: FTBFS randomly
has caused the Debian Bug report #841904,
regarding swift: FTBFS randomly (failing tests)
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.)


-- 
841904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:swift
Version: 2.10.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:59: warning: overriding recipe for target 'gen-init-configurations'
/usr/share/openstack-pkg-tools/pkgos.make:19: warning: ignoring old recipe for 
target 'gen-init-configurations'
debian/rules:69: warning: overriding recipe for target 
'override_dh_systemd_enable'
/usr/share/openstack-pkg-tools/pkgos.make:52: warning: ignoring old recipe for 
target 'override_dh_systemd_enable'
debian/rules:75: warning: overriding recipe for target 'override_dh_installinit'
/usr/share/openstack-pkg-tools/pkgos.make:55: warning: ignoring old recipe for 
target 'override_dh_installinit'
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils

[... snipped ...]

test_version_manifest_utf8_object 
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_version_manifest_utf8_version_container 
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_version_manifest_utf8_version_container_utf_object 
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_registered_defaults (test.unit.proxy.test_server.TestSwiftInfo) ... ok
test_PUT_sysmeta_then_GET (test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... 
ok
test_PUT_sysmeta_then_HEAD (test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... 
ok
test_sysmeta_not_updated_by_POST 
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_sysmeta_not_updated_by_POST_as_copy 
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_sysmeta_replaced_by_PUT (test.unit.proxy.test_sysmeta.TestObjectSysmeta) 
... ok
test_sysmeta_updated_by_COPY (test.unit.proxy.test_sysmeta.TestObjectSysmeta) 
... ok
test_sysmeta_updated_by_COPY_from 
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_transient_sysmeta_replaced_by_PUT_or_POST 
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_transient_sysmeta_replaced_by_PUT_or_POST_as_copy 
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_translations (test.unit.test_locale.test_locale.TestTranslations) ... ok

======================================================================
FAIL: test_hash_suffix_one_reclaim_tombstone_with_hash_pkl 
(test.unit.obj.test_diskfile.TestSuffixHashes)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/<<PKGBUILDDIR>>/test/unit/obj/test_diskfile.py", line 5485, in 
test_hash_suffix_one_reclaim_tombstone_with_hash_pkl
    self.assertGreater(os.stat(hash_file).st_mtime, hash_timestamp)
AssertionError: 1477294357.0770822 not greater than 1477294357.0770822
    """Fail immediately, with the given message."""
>>  raise self.failureException('1477294357.0770822 not greater than 
>> 1477294357.0770822')
    
-------------------- >> begin captured logging << --------------------
root: ERROR: Quarantined /tmp/tmpaBgQRG/node/sda1/objects/0/.lock to 
/tmp/tmpaBgQRG/node/quarantined/objects/0 because it is not a directory
Traceback (most recent call last):
  File "/<<PKGBUILDDIR>>/swift/obj/diskfile.py", line 922, in _hash_suffix_dir
    ondisk_info = self.cleanup_ondisk_files(hsh_path, reclaim_age)
  File "/<<PKGBUILDDIR>>/swift/obj/diskfile.py", line 877, in 
cleanup_ondisk_files
    files = listdir(hsh_path)
  File "/<<PKGBUILDDIR>>/swift/common/utils.py", line 3079, in listdir
    return os.listdir(path)
OSError: [Errno 20] Not a directory: '/tmp/tmpaBgQRG/node/sda1/objects/0/.lock'
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 4813 tests in 97.635s

FAILED (failures=1)
debian/rules:34: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

I'm attaching the full build log.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

Attachment: swift_2.10.0-3_amd64-20161024T073131Z.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Version: 2.10.1-1

After building version 2.10.1-1 about 50 times today without getting
any failure, this bug seems fixed.

Thanks.

--- End Message ---

Reply via email to