Your message dated Fri, 4 Mar 2016 18:41:17 -0300
with message-id <[email protected]>
and subject line Re: ruby-test-after-commit: FTBFS: undefined method `[]=' for
nil:NilClass
has caused the Debian Bug report #808515,
regarding ruby-test-after-commit: FTBFS: undefined method `[]=' for nil:NilClass
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 [email protected]
immediately.)
--
808515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808515
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-test-after-commit
Version: 0.2.3+gh-1
Severity: serious
Justification: fails to build from source
Tags: sid
User: [email protected]
Usertags: ftbfs
X-Debbugs-CC: [email protected]
Dear Maintainer,
The package fails to build:
DEPRECATION WARNING: Currently, Active Record suppresses errors raised within
`after_rollback`/`after_commit` callbacks and only print them to the logs. In
the next version, these errors will no longer be suppressed. Instead, the
errors will propagate normally just like in other Active Record callbacks.
You can opt into the new behavior and remove this warning by setting:
config.active_record.raise_in_transactional_callbacks = true
(called from <class:Address> at
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:141)
DEPRECATION WARNING: Currently, Active Record suppresses errors raised within
`after_rollback`/`after_commit` callbacks and only print them to the logs. In
the next version, these errors will no longer be suppressed. Instead, the
errors will propagate normally just like in other Active Record callbacks.
You can opt into the new behavior and remove this warning by setting:
config.active_record.raise_in_transactional_callbacks = true
(called from <class:Person> at
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:158)
DEPRECATION WARNING: Currently, Active Record suppresses errors raised within
`after_rollback`/`after_commit` callbacks and only print them to the logs. In
the next version, these errors will no longer be suppressed. Instead, the
errors will propagate normally just like in other Active Record callbacks.
You can opt into the new behavior and remove this warning by setting:
config.active_record.raise_in_transactional_callbacks = true
(called from <class:FuBear> at
/ruby-test-after-commit-0.2.3+gh/spec/database.rb:175)
.FFFFFFFF*FFFFF
...
Failures:
1) TestAfterCommit fires on create
Failure/Error: Car.create
NoMethodError:
undefined method `commit_records' for nil:NilClass
# ./lib/test_after_commit.rb:31:in `test_commit_records'
# ./lib/test_after_commit.rb:18:in `ensure in block in
transaction_with_transactional_fixtures'
# ./lib/test_after_commit.rb:20:in `block in
transaction_with_transactional_fixtures'
# ./lib/test_after_commit.rb:9:in `transaction_with_transactional_fixtures'
# ./spec/test_after_commit_spec.rb:18:in `block (2 levels) in <top
(required)>'
# ./spec/spec_helper.rb:25:in `block (2 levels) in <top (required)>'
2) TestAfterCommit fires on update
Failure/Error: car = Car.create
NoMethodError:
undefined method `[]=' for nil:NilClass
# ./lib/test_after_commit.rb:72:in `sync_with_transaction_state'
# ./lib/test_after_commit.rb:12:in `block in
transaction_with_transactional_fixtures'
# ./lib/test_after_commit.rb:9:in `transaction_with_transactional_fixtures'
# ./spec/test_after_commit_spec.rb:23:in `block (2 levels) in <top
(required)>'
# ./spec/spec_helper.rb:25:in `block (2 levels) in <top (required)>'
...
Failed examples:
rspec ./spec/test_after_commit_spec.rb:17 # TestAfterCommit fires on create
rspec ./spec/test_after_commit_spec.rb:22 # TestAfterCommit fires on update
rspec ./spec/test_after_commit_spec.rb:29 # TestAfterCommit fires on
update_attribute
rspec ./spec/test_after_commit_spec.rb:36 # TestAfterCommit does not fire on
rollback
rspec ./spec/test_after_commit_spec.rb:43 # TestAfterCommit does not fire on
ActiveRecord::RecordInvalid
rspec ./spec/test_after_commit_spec.rb:50 # TestAfterCommit does not fire
multiple times in nested transactions
rspec ./spec/test_after_commit_spec.rb:61 # TestAfterCommit fires when
transaction block returns from method
rspec ./spec/test_after_commit_spec.rb:66 # TestAfterCommit does not raises
errors
rspec ./spec/test_after_commit_spec.rb:90 # TestAfterCommit returns on create
and on create of associations
rspec ./spec/test_after_commit_spec.rb:95 # TestAfterCommit returns on create
and on create of associations without after_commit
rspec ./spec/test_after_commit_spec.rb:100 # TestAfterCommit calls callbacks in
correct order
rspec ./spec/test_after_commit_spec.rb:110 # TestAfterCommit Observer should
record commits
rspec ./spec/test_after_commit_spec.rb:123 # TestAfterCommit nested
after_commit is executed
/usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install
/ruby-test-after-commit-0.2.3+gh/debian/ruby-test-after-commit returned exit
code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary gave error exit status 2
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-test-after-commit.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
fixed 808515 0.4.2-1
thanks
Fixed in 0.4.2-1
Cheers,
Seb
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
