[DRE-maint] Bug#759918: ruby-activerecord-nulldb-adapter: FTBFS: ERROR: Test "ruby2.1" failed: Failure/Error: cxn.select_values("")

[Lucas Nussbaum]

Source: ruby-activerecord-nulldb-adapter
Version: 0.3.1-1
Severity: serious
Tags: jessie sid
User: debian-qa at 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):
>      Failure/Error: cxn.select_values("")
>      ArgumentError:
>        wrong number of arguments (3 for 1..2)
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:161:in `select_rows'
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:208:in `block in select_values'
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:239:in `block in with_entry_point'
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:254:in `with_thread_local_variable'
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:238:in `with_entry_point'
>      # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:207:in `select_values'
>      # ./spec/nulldb_spec.rb:234:in `block (2 levels) in <top (required)>'
> 
> Finished in 0.03349 seconds
> 33 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/nulldb_spec.rb:110 # NullDB should remember columns defined in migrations
> rspec ./spec/nulldb_spec.rb:204 # NullDB should tag logged statements with their entry point
> /usr/bin/ruby2.1 -S rspec ./spec/nulldb_spec.rb failed
> ERROR: Test "ruby2.1" failed: 

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-activerecord-nulldb-adapter_0.3.1-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.