Your message dated Tue, 4 Nov 2014 11:47:26 -0500
with message-id <20141104164726.ga30...@onerussian.com>
and subject line looks like fixed in 0.21.1
has caused the Debian Bug report #755340,
regarding cython: FTBFS: Tests failures
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 ow...@bugs.debian.org
immediately.)
--
755340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cython
Version: 0.20.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140718 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):
> ======================================================================
> ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/«PKGBUILDDIR»/Cython/Debugger/Tests/TestLibCython.py", line 281, in
> test_all
> sys.stderr.write(errmsg)
> UnicodeEncodeError: 'ascii' codec can't encode characters in position
> 21072-21075: ordinal not in range(128)
>
> ----------------------------------------------------------------------
> Ran 8339 tests in 2258.934s
>
> FAILED (errors=1)
> ALL DONE
> make[1]: *** [override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/07/18/cython_0.20.2-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.
--- End Message ---
--- Begin Message ---
Version: 0.21.1-1
I did manage to replicate such an issue before on some builds:
$ grep "codec can't encode characters in position" 0.2*/*build
0.20.1+git90-g0e6e38e-1/cython_0.20.1+git90-g0e6e38e-1~nd70+1_i386.build:UnicodeEncodeError:
'ascii' codec can't encode characters in position 19661-19664: ordinal not in
range(128)
0.20.2-1/cython_0.20.2-1~nd70+1_i386.build:UnicodeEncodeError: 'ascii' codec
can't encode characters in position 18851-18854: ordinal not in range(128)
0.20.2+git216-ga96882e-1/cython_0.20.2+git216-ga96882e-1~nd70+1_i386.build:UnicodeEncodeError:
'ascii' codec can't encode characters in position 21001-21004: ordinal not in
range(128)
but as you can see there were no hit in 0.21.1-1 so closing
Please reopen if it strikes back
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--- End Message ---
