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