buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-256) Automatically installing gems aborts rspec test runner
Date Thu, 08 Jul 2010 03:13:49 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886211#action_12886211
] 

Hudson commented on BUILDR-256:
-------------------------------

Integrated in Buildr-ci-build #53 (See [http://hudson.zones.apache.org/hudson/job/Buildr-ci-build/53/])
    fix for BUILDR-256 and BUILDR-342


> Automatically installing gems aborts rspec test runner
> ------------------------------------------------------
>
>                 Key: BUILDR-256
>                 URL: https://issues.apache.org/jira/browse/BUILDR-256
>             Project: Buildr
>          Issue Type: Bug
>    Affects Versions: 1.3.3
>         Environment: RubyGems 1.2.0
>            Reporter: Rhett Sutphin
>            Assignee: Antoine Toulme
>            Priority: Minor
>             Fix For: 1.4.2
>
>
> The automatic jruby gem installer code (the template for which is created by the jruby_gem
method in TestFramework::JRubyBased) uses Gem::GemRunner to automatically install gems.  GemRunner
(at least in RubyGems 1.2.0) always throws Gem::SystemExitException when it completes.  This
aborts the runner and returns control to buildr.  Buildr then fails with an exception because
result.yaml doesn't exist.
> Workaround: each run will successfully install one of the gems, so you can run the test
several times to install all the gems.  Alternatively, you can manually install the necessary
gems using jruby -S gem install.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message