Your message dated Sun, 05 Oct 2014 15:11:19 +0200 with message-id <2751906.1yOaaDVCff@sephirot> and subject line Builds fine has caused the Debian Bug report #759905, regarding ruby-rabl-rails: FTBFS: ERROR: Test "ruby2.1" failed: Running tests for ruby2.1 using debian/ruby-tests.rake ... 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.) -- 759905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-rabl-rails Version: 0.3.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): > Running tests for ruby2.1 using debian/ruby-tests.rake ... > /usr/bin/ruby2.1 -I"lib:lib:test" -I"/usr/lib/ruby/vendor_ruby" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" > Run options: --seed 9834 > > # Running: > > .......................................................................................................FFFFF.F. > > Finished in 0.273967s, 405.1586 runs/s, 452.6097 assertions/s. > > 1) Failure: > DeepNestingTest#test_compile_and_render_deep_nesting_template > [/«PKGBUILDDIR»/test/deep_nesting_test.rb:41]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"id\":1,\"name\":\"foobar\",\"posts\":[{\"title\":\"I rock > !\",\"comments\":[{\"content\":\"first\"},{\"content\":\"second\"}]}]}}" > +"{\"id\":1,\"name\":\"foobar\",\"posts\":[{\"title\":\"I rock > !\",\"comments\":[{\"content\":\"first\"},{\"content\":\"second\"}]}]}" > > > > 2) Failure: > RenderTest#test_allow_object_to_be_passed_as_an_option > [/«PKGBUILDDIR»/test/render_test.rb:19]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"name\":\"Marty\"}}" > +"{\"name\":\"Marty\"}" > > > > 3) Failure: > RenderTest#test_format_can_be_omitted_if_option_is_set > [/«PKGBUILDDIR»/test/render_test.rb:86]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"id\":1,\"name\":\"Marty\"}}" > +"{\"id\":1,\"name\":\"Marty\"}" > > > > 4) Failure: > RenderTest#test_format_can_be_passed_as_symbol_or_a_string > [/«PKGBUILDDIR»/test/render_test.rb:71]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"id\":1,\"name\":\"Marty\"}}" > +"{\"id\":1,\"name\":\"Marty\"}" > > > > 5) Failure: > RenderTest#test_handle_path_for_extends > [/«PKGBUILDDIR»/test/render_test.rb:60]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"extended_name\":\"Marty\"}}" > +"{\"extended_name\":\"Marty\"}" > > > > 6) Failure: > RenderTest#test_load_source_from_file [/«PKGBUILDDIR»/test/render_test.rb:29]: > --- expected > +++ actual > @@ -1 +1 @@ > -"{\"user\":{\"id\":1,\"name\":\"Marty\"}}" > +"{\"id\":1,\"name\":\"Marty\"}" > > > 111 runs, 124 assertions, 6 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -I"lib:lib:test" > -I"/usr/lib/ruby/vendor_ruby" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" ] > -e:1:in `<main>' > 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/2014/08/30/ruby-rabl-rails_0.3.4-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. The build was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure.
--- End Message ---
--- Begin Message ---Now builds ok; closing it. -- David
--- End Message ---
