[rspec-devel] [ rspec-Bugs-6112 ] Rspec on Rails: Postgresql reports WARNING: there is already a transaction in progress

[noreply at rubyforge.org]

Bugs item #6112, was opened at 2006-10-13 00:35
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3149&aid=6112&group_id=797

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: David Lee (davidlee)
Assigned to: Nobody (None)
Summary: Rspec on Rails: Postgresql reports WARNING: there is already a transaction in progress

Initial Comment:
This has been verified on Arch Linux (gimmick) and OS X Tiger (postgres 8.1 via darwinports), using Rails 1.1.2 and RSpec 0.6.4 & the rspec rails plugin.

Description (output from skeletal rails project):

/tmp/foo % spec spec/models/tester_spec.rb 

WARNING:  there is already a transaction in progress
WARNING:  there is no transaction in progress
.WARNING:  there is already a transaction in progress
WARNING:  there is no transaction in progress
F

1)
Spec::Expectations::ExpectationNotMetError in 'Tester class with fixtures loaded should have more specifications'
not enough specs
./spec/models/tester_spec.rb:11:in `should have more specifications'

Finished in 0.326214 seconds

2 specifications, 1 failure

____

2 lines of warnings are generated per specify block.

When running a substantial spec, voluminous WARNINGs are generated, such that it is necessary to run 

spec spec/models/* 2> /dev/null

to prevent the test output being lost in noise.

----------------------------------------------------------------------

>Comment By: David Lee (davidlee)
Date: 2006-12-12 21:54

Message:
This no longer seems to be an issue with the current
release, on account of it being substantially rewritten and
choc full of awesome.

----------------------------------------------------------------------

Comment By: David Chelimsky (dchelimsky)
Date: 2006-12-08 13:27

Message:
David - is this still a problem with 0.7.4? Things have changed quite a bit since 0.6.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3149&aid=6112&group_id=797