TwP/logging — Issue #19: Unable to run tests
Author: martinos
Created: 2011-12-30 16:59:16+00:00
State: open

When I try to run the `rake test` task I get the following error:

```
/myhome/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/ext/module.rb:36:in `const_missing': uninitialized constant Logging::RUBY_ENGINE (NameError)
from /myhome/dev/gems/logging/lib/logging/log_event.rb:16
from /myhome/dev/gems/logging/lib/logging/log_event.rb:6:in `new'
from /myhome/dev/gems/logging/lib/logging/log_event.rb:6
from /myhome/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
from /myhome/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
from /myhome/dev/gems/logging/test/../lib/logging.rb:520
from /myhome/dev/gems/logging/test/../lib/logging.rb:374:in `call'
from /myhome/dev/gems/logging/test/../lib/logging.rb:374:in `libpath'
from /myhome/dev/gems/logging/test/../lib/logging.rb:517
from /myhome/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
from /myhome/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
from /myhome/dev/gems/logging/test/setup.rb:18
from /myhome/dev/gems/logging/test/appenders/test_buffered_io.rb:2:in `require'
from /myhome/dev/gems/logging/test/appenders/test_buffered_io.rb:2
from /myhome/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:15:in `require'
from /myhome/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:15
from /myhome/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:4:in `select'
from /myhome/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/rake_test_loader.rb:4
```
I am running ruby 1.8.7 and my gemset is

```
bones (3.7.3)
bones-git (1.2.4)
bones-rcov (1.0.1)
flexmock (0.9.0)
git (1.2.5)
json (1.6.4)
little-plugger (1.1.3)
loquacious (1.9.1)
rake (0.8.7)
rcov (0.9.11)
rdoc (3.12)
```
Do you have an idea of what might be the cause of this issue ?