Control: tags -1 unreproducible moreinfo
Control: severity -1 important
Hi Christian,
On Wed, 08 Jul 2015 12:57:05 +0200 Christian Hofstaedtler
<z...@debian.org> wrote:
> Source: ruby-bert
> Version: 1.1.6-1
> Severity: serious
> Justification: fails to build from source
>
> Dear Maintainer,
>
> your package FTBFS, but built in the past.
>
> Relevant snippet from the build log:
>
> RUBYLIB=/«PKGBUILDDIR»/debian/ruby-bert/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0:/«PKGBUILDDIR»/debian/ruby-bert/usr/lib/ruby/vendor_ruby:.
> ruby2.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> *** Error in `ruby2.1': munmap_chunk(): invalid pointer: 0x00007fcf31e78e30
> ***
> /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:115:in `exit': no implicit
> conversion from nil to integer (TypeError)
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:115:in
> `run_ruby'
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:162:in
> `do_run_tests'
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:69:in
> `run_tests'
> from /usr/bin/gem2deb-test-runner:53:in `<main>'
> ERROR: Test "ruby2.1" failed. Exiting.
I could not reproduce the issue in a clean unstable chroot using sbuild
today by building the package three times.
I see similar crashes on sparc and ppc64 [1] thus the problem may not
appear all the time or is in a build-depenency. I'm decreasing severity
for now, but I'm also checking if Valgrind finds something during the build.
Cheers,
Balint
[1] https://buildd.debian.org/status/package.php?p=ruby-bert&suite=unstable
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
