Source: nsscache Version: 0.32-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > .........................................................................................................................................................................................................................F............................................. > ====================================================================== > FAIL: testGetSingleMapMetadataTimestampEpochFalse > (nss_cache.command_test.TestStatusCommand) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/mox.py", line 1870, in new_method > func(self, *args, **kwargs) > File "/<<PKGBUILDDIR>>/nss_cache/command_test.py", line 817, in > testGetSingleMapMetadataTimestampEpochFalse > values[1]['value']) > AssertionError: 'Wed Dec 31 16:00:02 1969' != 'Thu Jan 1 00:00:02 1970' > > ---------------------------------------------------------------------- > Ran 263 tests in 0.238s > > FAILED (failures=1) > debian/rules:11: recipe for target 'override_dh_auto_test' failed If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/01/nsscache_0.32-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
