Your message dated Mon, 29 Oct 2018 23:09:16 +0200
with message-id <20181029210916.GB24921@localhost>
and subject line This seems to be already fixed in experimental
has caused the Debian Bug report #912274,
regarding ruby-clockwork FTBFS: Mocha::NotInitializedError: Mocha methods
cannot be used outside the context of a test
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.)
--
912274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-clockwork
Version: 1.2.0-3
Severity: serious
Tags: ftbfs
ruby-clockwork fails to build from source in unstable.
| 1) Error:
| Clockwork::Event::#thread?::manager config thread option set to
true#test_0001_is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/event_test.rb:12:in `block (4 levels) in <top
(required)>'
|
| 2) Error:
| Clockwork::Event::#thread?::manager config thread option set to
true#test_0002_is false when event thread option set:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/event_test.rb:12:in `block (4 levels) in <top
(required)>'
|
| 3) Error:
| Clockwork::Manager#test_0013_exceptions still set the last timestamp to avoid
spastic error loops:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/manager_test.rb:131:in `block (2 levels) in <top
(required)>'
|
| 4) Error:
| Clockwork#test_0006_support module re-open style:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:80:in `block (2 levels) in <top
(required)>'
|
| 5) Error:
| Clockwork#test_0001_should run events with configured logger:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:24:in `block (2 levels) in <top
(required)>'
|
| 6) Error:
| Clockwork#test_0002_should log event correctly:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:37:in `block (2 levels) in <top
(required)>'
|
| 7) Error:
| Clockwork#test_0004_should not run anything after reset:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:62:in `block (2 levels) in <top
(required)>'
|
| 8) Error:
| Clockwork#test_0003_should pass event without modification to handler:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:50:in `block (2 levels) in <top
(required)>'
|
| 9) Error:
| Clockwork#test_0005_should pass all arguments to every:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/clockwork_test.rb:69:in `block (2 levels) in <top
(required)>'
|
| 10) Error:
| Clockwork::Event::#thread?::manager config thread option not set#test_0001_is
true if event thread option is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/event_test.rb:28:in `block (4 levels) in <top
(required)>'
|
| 11) Error:
| Clockwork::Manager::max_threads#test_0001_should warn when an event tries to
generate threads more than max_threads:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/manager_test.rb:276:in `block (3 levels) in <top
(required)>'
|
| 12) Error:
| Clockwork::Manager::max_threads#test_0002_should not warn when thread is
managed by others:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context
of a test
| /<<PKGBUILDDIR>>/test/manager_test.rb:291:in `block (3 levels) in <top
(required)>'
|
| 85 runs, 139 assertions, 0 failures, 12 errors, 0 skips
| rake aborted!
| Command failed with status (1): [ruby -w -I"test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/at_test.rb"
"test/clockwork_test.rb" "test/database_events/sync_performer_test.rb"
"test/event_test.rb" "test/manager_test.rb"
"test/database_events/test_helpers.rb" -v]
|
| Tasks: TOP => default
| (See full trace by running task with --trace)
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-clockwork
returned exit code 1
| make: *** [debian/rules:6: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
Helmut
--- End Message ---
--- Begin Message ---
Version: 2.0.3-1
This seems to be already fixed in experimental:
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/ruby-clockwork.html
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--- End Message ---
