[
https://issues.apache.org/jira/browse/BUILDR-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610015#comment-13610015
]
Niklaus Giger commented on BUILDR-662:
--------------------------------------
On my machines the overhead for jruby varies between 2 and 7 seconds for a
command like 'time rvm jruby-1.6.7.2 do buildr --help'.
But the reported time difference with 2 minutes is much larger!
And 7 seconds is already bad if you just want to test a small build, but for my
larger builds they are not significant. And I had some weird problems switching
to another ruby (and no time to debug them).
> reported time is much shorter than actual
> -----------------------------------------
>
> Key: BUILDR-662
> URL: https://issues.apache.org/jira/browse/BUILDR-662
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.4.9
> Environment: jruby Debian
> Reporter: Niklaus Giger
>
> When I run my Tests (using jruby 1.6.7.2) buildr reports:
> "Completed in 5m23.715s"
> Output of time command is
> real 7m16.347s
> user 9m15.783s
> sys 0m34.774s
> Looks as if buildr is cheating. Does it start the timer only after analysing
> the dependencies?
> Seen .eg. in my Jenkins build
> http://ngiger.dyndns.org/jenkins/job/elexis-2.1.7-Buildr/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
