[rspec-users] Sudden rspec problem

Rich Price rich at gandalf.ws
Sun Jan 16 20:10:31 EST 2011


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.

On 01/16/2011 06:48 PM, Rich Price wrote:
> 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.
>
> On 01/16/2011 05:51 PM, Mike Mazur wrote:
>> Hi,
>>
>> On Mon, Jan 17, 2011 at 06:47, Rich Price<rich at gandalf.ws> wrote:
>>> I was using rspec 2.4.0 to test some code
>>> and it was working fine then suddenly I get
>>>
>>> rich at 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:in `require'
>>> 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:in
>>>
>>> `load_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:in
>>>
>>> `load_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:in
>>> `run_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:in
>>> `autorun'
>>> from /var/lib/gems/1.8/rspec:19
>>> rich at 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
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


More information about the rspec-users mailing list