Your message dated Wed, 04 Feb 2015 22:06:06 +0000
with message-id <e1yj85g-0001b6...@franck.debian.org>
and subject line Bug#775631: fixed in ruby-pygments.rb 0.5.4~ds1-2
has caused the Debian Bug report #775631,
regarding ruby-pygments.rb: FTBFS in jessie: ERROR: Test "ruby2.1" failed: 
Running tests for ruby2.1 using debian/ruby-tests.rb...
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.)


-- 
775631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-pygments.rb
Version: 0.5.4~ds1-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20150117 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> Running tests for ruby2.1 using debian/ruby-tests.rb...
> Run options: 
> 
> # Running tests:
> 
> ....................F...........................
> 
> Finished tests in 9.125198s, 5.2602 tests/s, 10.7395 assertions/s.
> 
>   1) Failure:
> PygmentsHighlightTest#test_highlight_works_with_larger_files 
> [/«PKGBUILDDIR»/test/test_pygments.rb:35]:
> <455203> expected but was
> <451844>.
> 
> 48 tests, 98 assertions, 1 failures, 0 errors, 0 skips
> 
> ruby -v: ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]
> rake aborted!
> Command failed with status (1): [ruby -I"lib" -rubygems 
> -I"/usr/lib/ruby/vendor_ruby" 
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_pygments.rb" ]
> 
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2015/01/17/ruby-pygments.rb_0.5.4~ds1-1.1_jessie.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 ---
Source: ruby-pygments.rb
Source-Version: 0.5.4~ds1-2

We believe that the bug you reported is fixed in the latest version of
ruby-pygments.rb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro <terce...@debian.org> (supplier of updated ruby-pygments.rb 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 04 Feb 2015 19:43:57 -0200
Source: ruby-pygments.rb
Binary: ruby-pygments.rb
Architecture: source all
Version: 0.5.4~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Description:
 ruby-pygments.rb - pygments wrapper for Ruby
Closes: 775631
Changes:
 ruby-pygments.rb (0.5.4~ds1-2) unstable; urgency=medium
 .
   * Team upload
   * fix tests (Closes: #775631):
     - test_highlight_works_with_larger_files: instead of testing for an exact
       amount of bytes, pass with there are more than 400,000 of them.
       (debian/patches/0007-Update-test-result.patch)
     - test_highlight_works_with_single_character_input: removed, since the
       underlying Python code does not support that use case.
       (debian/patches/0008-Drop-unfeasible-test.patch)
Checksums-Sha1:
 4a00523c5378bf9ddad4c7a654b29d915f7b03d5 2149 ruby-pygments.rb_0.5.4~ds1-2.dsc
 5969b449985337b5be8500126f66ada36fcd1478 7104 
ruby-pygments.rb_0.5.4~ds1-2.debian.tar.xz
 54e0b1b14a0bcb4c241bcafddd192fd28a8f6f60 278284 
ruby-pygments.rb_0.5.4~ds1-2_all.deb
Checksums-Sha256:
 ba1ae96029e7fc2884f438bb417ba9f3fe1b29da44e119397e5e81defc2e1817 2149 
ruby-pygments.rb_0.5.4~ds1-2.dsc
 8ae5eb7ff5c89d53952440ba62176ede3123d194163266cf4eaff7b416e04823 7104 
ruby-pygments.rb_0.5.4~ds1-2.debian.tar.xz
 9b205935ce76d485dc7b40eb511972ea09bee2cf01235c4ab75c17169929e48b 278284 
ruby-pygments.rb_0.5.4~ds1-2_all.deb
Files:
 9135c268653c2d9f833f8dee6d9d8876 2149 ruby optional 
ruby-pygments.rb_0.5.4~ds1-2.dsc
 929f9d87117beccc7bfdf1a951e0a4e9 7104 ruby optional 
ruby-pygments.rb_0.5.4~ds1-2.debian.tar.xz
 58b34e63d8eb3286f7e31ae5548057d3 278284 ruby optional 
ruby-pygments.rb_0.5.4~ds1-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU0pMtAAoJEPwNsbvNRgvewogQAOUV9yRgNo3VQc+KYjMxQFCI
igiSPXQ7VGei5+oysVMvhjhirwnO6AqPTezEbWvGMz19oL9sdZaMp3eZLEZGXta5
0+X6XJXi8B4kTAUXnOHfRaBzgzAUk76JxWvOGEQhkkiHiAC3ymQBNZ4veeZDPRrJ
WatTPZ9zs8awUBPJrC2yIZx4AOMbXxFYGZuoT8gdNGU3X33Iw5O6Xjc3SiMzpoer
zaRvLQemh58F+2adp4HyIEgLB7iddo71onWzFAmWN0E0leXKICmTdt2Htjl2Nv7F
0KfYJMAwVDtyk7FM7dgPGVCUR88L3G2iWPfO6diNLhOd1zWfzxlXtRQ3R4Jv/1jm
oX/d+TfIhoRN9+fsd6vg7ecqeSNWuHzrPNXp8SY3DUMIVPFwIuxP3+/7cD3vUxML
YcC/+eWDerlSABjeRm9LzBHZ5ixUs0Az/zhblMWGYb8Rysewo3mA8ijBgJBxBFRp
U6f+up2xTQ9wpo3v2MSEpCc6mk72gk9bNgUFColqQROZCGLVwIuYwOUfI62UysQK
hO1pufRck9qsVxfwjNt8373oReueX4AHBd0TDiFZSZw2Cyiz5VsQKw1mKHwpvfNx
IqhJKcCHtNxNL53iMoDPNdd4G55UlwxZeFVUPFhz/bwV+Kl/D63Wh4XFn4EiVMyU
F8gQVG/GDdmWZv8OXIRP
=g8pI
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to