Sudden rspec problem

Testing RSpec
1

I was using rspec 2.4.0 to test some code
and it was working fine then suddenly I get

rich@richlaptop2:~/Documents/fakemap/rspec$ rspec block.rb
/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require': ../code/fmutil.rb:145: class/module name must be CONSTANT (SyntaxError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:inrequire’
from /home/rich/Documents/fakemap/rspec/block.rb:1
from
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/configuration.rb:387:in
load' from /var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/configuration.rb:387:inload_spec_files’
from
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/configuration.rb:387:in
map' from /var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/configuration.rb:387:inload_spec_files’
from
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/command_line.rb:18:in
run' from /var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/runner.rb:55:inrun_in_process’
from
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/runner.rb:46:in
run' from /var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/runner.rb:10:inautorun’
from /var/lib/gems/1.8/rspec:19
rich@richlaptop2:~/Documents/fakemap/rspec$

This is for code that was ENTIRELY unchanged
from a previous successful test.

Now any use that I make of rspec produces these errors!

Has anyone seen behavior like this?
Is theis a known bug with rspec?

Rich P.
[email protected]

2

On Jan 16, 2011, at 4:47 PM, Rich P. wrote:

from
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/configuration.rb:387:in
`load_spec_files’
Now any use that I make of rspec produces these errors!

Has anyone seen behavior like this?
Is theis a known bug with rspec?

What’s on line 1 of block.rb?

3

Hi,

On Mon, Jan 17, 2011 at 06:47, Rich P. [email protected] wrote:

`load’
/var/lib/gems/1.8/gems/rspec-core-2.4.0/lib/rspec/core/command_line.rb:18:in
rich@richlaptop2:~/Documents/fakemap/rspec$

This is for code that was ENTIRELY unchanged
from a previous successful test.

Now any use that I make of rspec produces these errors!

Has anyone seen behavior like this?
Is theis a known bug with rspec?

I notice the error happens in rubygems/custom_require.rb and that
you’re using rspec-core from a global gem directory. Could it be that
you upgraded some gems recently? Perhaps this gem is also a dependency
for your project and it has a bug. What does
/home/rich/Documents/fakemap/rspec/block.rb line 1 contain?

Mike

4

OK - I found the problem.

While correcting the spelling of a class
name in fmutil.rb I lost the leading capital
letter. Oh! The embarrassment! Thanks.

5

The first two lines are:
require ‘…/code/fmutil.rb’
require ‘…/code/fmgrid.rb’

I had not updated any gems between the test that worked and the
one that produced these results.