Source: ycmd
Version: 0+20160327+gitc3e6904-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> Ran 509 tests in 1.258s
> 
> FAILED (SKIP=11, errors=7, failures=6)
> Running tests on Python 2.7.12+
> Running flake8
> Traceback (most recent call last):
>   File "./run_tests.py", line 218, in <module>
>     Main()
>   File "./run_tests.py", line 215, in Main
>     NoseTests( parsed_args, nosetests_args )
>   File "./run_tests.py", line 206, in NoseTests
>     subprocess.check_call( [ 'nosetests' ] + nosetests_args )
>   File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
>     raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '[u'nosetests', u'-v', u'--with-id', 
> '--no-byte-compile', '--exclude=^cs$', '--exclude=UnknownExtraConfException', 
> '--exclude=javascript', '--exclude=rust', '--exclude=go']' returned non-zero 
> exit status 1
> debian/rules:40: 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/21/ycmd_0+20160327+gitc3e6904-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.

Reply via email to