[
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.
