You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Rhett Sutphin (JIRA)" <ji...@apache.org> on 2009/02/16 23:04:59 UTC
[jira] Created: (BUILDR-252) Rspec test runner fails after first
file when running an entire suite
Rspec test runner fails after first file when running an entire suite
---------------------------------------------------------------------
Key: BUILDR-252
URL: https://issues.apache.org/jira/browse/BUILDR-252
Project: Buildr
Issue Type: Bug
Components: Test frameworks
Affects Versions: 1.3.3
Environment: OS X 10.5 built-in ruby (running buildr)
JRuby 1.1.3 (running rspec in buildr)
Reporter: Rhett Sutphin
I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
8 examples, 0 failures, 1 pending
/Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
The exception happens whether or not the first file has any failing specs in it.
If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rhett Sutphin updated BUILDR-252:
---------------------------------
Summary: Rspec test runner fails after first pending spec (was: Rspec test runner fails after first file when running an entire suite)
The actual problem is not with spec files, but rather with pending specs. Rspec-1.1.4 is throwing an exception when it hits a pending spec:
--- !ruby/exception:Buildr::TestFramework::TestResult::Error
backtrace:
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/reporter.rb:110:in
`example_pending'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/reporter.rb:110:in
`example_pending'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/reporter.rb:109:in
`each'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/reporter.rb:109:in
`example_pending'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/reporter.rb:29:in
`example_finished'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/example/example_methods.rb:32:in
`execute'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/example/example_group_methods.rb:303:in
`execute_examples'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/example/example_group_methods.rb:302:in
`each'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/example/example_group_methods.rb:302:in
`execute_examples'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/example/example_group_methods.rb:130:in
`run'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:22:in
`run'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:21:in
`each'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/example_group_runner.rb:21:in
`run'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/options.rb:106:in
`run_examples'
- /Users/rsutphin/.jruby/lib/ruby/gems/1.8/gems/rspec-1.1.4/lib/spec/runner/command_line.rb:19:in
`run'
- [...]/test/restful-api/target/spec/runner.rb:35
- /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:41:in `guard'
- [...]/test/restful-api/target/spec/runner.rb:34
message: wrong number of arguments(2 for 3)
The 1 for 2 wrong number of arguments error above was hiding this error. So both the error handling of the rspec TestFramework and whatever is causing this rspec exception need to be addressed.
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rhett Sutphin updated BUILDR-252:
---------------------------------
Fix Version/s: 1.3.4
The separate rspec install bug is BUILDR-254
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
> Fix For: 1.3.4
>
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin closed BUILDR-252.
------------------------------
Resolution: Won't Fix
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
> Fix For: 1.3.4
>
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674321#action_12674321 ]
Rhett Sutphin commented on BUILDR-252:
--------------------------------------
That makes some sense -- I manually installed cucumber in jruby and then found that I got the same failure for hoe, manually installed hoe and got the suite to run. It's curious that the rspec gem's install dependencies are different from it's runtime dependencies, but I guess that's probably a bug in either hoe or in rspec's use of it.
So, to summarize -- the pending-spec-causes-failure bug is not present in trunk/1.3.4. There is another bug in trunk related to the automatic installation of rspec 1.1.12. I'll open a separate ticket for that.
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674309#action_12674309 ]
Assaf Arkin commented on BUILDR-252:
------------------------------------
I'm guessing two different versions of RubyGems, one that can tell the difference between runtime/dev dependencies, one that doesn't. If you look at the spec file (in gems/1.8/specifications), it will read:
if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then
s.add_development_dependency(%q<cucumber>, [">= 0.1.13"])
s.add_development_dependency(%q<hoe>, [">= 1.8.2"])
else
s.add_dependency(%q<cucumber>, [">= 0.1.13"])
s.add_dependency(%q<hoe>, [">= 1.8.2"])
end
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674324#action_12674324 ]
Assaf Arkin commented on BUILDR-252:
------------------------------------
Thanks!
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674110#action_12674110 ]
Assaf Arkin commented on BUILDR-252:
------------------------------------
Can you try this against trunk? I'm hoping we can upgrade to RSpec 1.1.12, which is not entirely backwards compatible with 1.1.4.
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674303#action_12674303 ]
Rhett Sutphin commented on BUILDR-252:
--------------------------------------
I noticed with trunk buildr and rspec 1.1.12, buildr was reinstalling the rspec gem in jruby on every test run. I traced this back to the automatic installer code in TestFramework::JRubyBased#jruby_gem. It is throwing a load error "Could not find RubyGem cucumber (>= 0.1.13)" when the rspec gem is loaded. The automatic installer code interprets the load error to mean that rspec isn't installed, so it reinstalls it. Then it requires it again and it fails again, but this time the exception bubbles out and kills the test run. This is why result.yaml wasn't being written.
I'm not sure what the deal is with the rspec gem. I get the same behavior when I install it manually under jruby -- it doesn't install cucumber itself, but then if I require the rspec gem in irb, it throws the same "Could not find RubyGem cucumber" error. Under matz ruby, installing the rspec 1.1.12 gem does not install cucumber and it also doesn't complain if it isn't present. The rspec gemspec has a dev dependency on cucumber, but I'm not sure why that would cause the different behavior on jruby and ruby that I'm seeing.
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-252) Rspec test runner fails after first
pending spec
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674277#action_12674277 ]
Rhett Sutphin commented on BUILDR-252:
--------------------------------------
First note: I'm using the jruby that buildr offered to install for me (in ~/.jruby). Rspec 1.1.4 was installed there automatically under buildr 1.3.3. When I first ran with trunk, buildr didn't automatically update that gem to Rspec 1.1.12, so I continued to get the exception above on the first pending spec. I uninstalled 1.1.4 manually, then buildr-trunk installed 1.1.12 automatically.
Now when I run the suite, the result.yaml file is not being created, resulting in this exception on the console (with --trace):
Test framework error: No such file or directory - [...]/test/restful-api/target/spec/result.yaml
/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/java/bdd.rb:108:
in `read'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/java/bdd.rb:108:
in `run'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:446:
in `run_tests'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:199:
in `initialize'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:
in `call'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:
in `execute'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:
in `each'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:
in `execute'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:227:
in `execute'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:638:
in `invoke_with_call_chain'/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:
in `synchronize'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:624:
in `invoke_with_call_chain'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:619:
in `invoke'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:164:
in `run_local_tests'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:161:
in `each'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:161:
in `run_local_tests'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/project.rb:349:
in `[]'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/project.rb:349:
in `local_projects'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/project.rb:349:
in `each'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/project.rb:349:
in `local_projects'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:158:
in `run_local_tests'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:501:
in `initialize'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:
in `call'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:
in `execute'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:
in `each'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:
in `execute'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/test.rb:508:
in `execute'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:638:
in `invoke_with_call_chain'/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:
in `synchronize'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:624:
in `invoke_with_call_chain'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:619:
in `invoke'/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:
in `invoke_task'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:232:
in `top_level'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:232:
in `each'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:232:
in `top_level'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:504:
in `standard_exception_handling'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:223:
in `top_level'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:138:
in `run'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:504:
in `standard_exception_handling'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/lib/buildr/core/application.rb:135:
in `run'/Library/Ruby/Gems/1.8/gems/buildr-1.3.4/bin/buildr:19/usr/bin/buildr:19:
in `load'/usr/bin/buildr:19
(Side note: buildr prints this backtrace all on one line. I've reformatted it to make it easier to read.)
The exception report is followed by "The following tests failed:" listing all the specs in the suite. However, I'm pretty sure they didn't run at all -- it returned much too quickly.
I presume the real problem is whatever is causing the result.yaml file not to be written, but I haven't tracked that down yet.
> Rspec test runner fails after first pending spec
> ------------------------------------------------
>
> Key: BUILDR-252
> URL: https://issues.apache.org/jira/browse/BUILDR-252
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: OS X 10.5 built-in ruby (running buildr)
> JRuby 1.1.3 (running rspec in buildr)
> Reporter: Rhett Sutphin
>
> I have an application with an integrated test suite which is using(:rspec). If I run the full suite (i.e., with `buildr integration`), it fails after the first spec file with an exception like this:
> 8 examples, 0 failures, 1 pending
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `dump_yaml': wrong number of arguments(1 for 2) (ArgumentError)
> from /Library/Ruby/Gems/1.8/gems/buildr-1.3.3/lib/buildr/java/test_result.rb:43:in `guard'
> from /Users/rsutphin/studycalendar/git/trunk/test/restful-api/target/spec/runner.rb:34
> The exception happens whether or not the first file has any failing specs in it.
> If I only run one spec (i.e., with `buildr integration:foo_spec` where foo_spec only matches one spec file), it does not fail. If I use a pattern which matches multiple specs, it fails with the same exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.