> Oh yeah, test-all is a brute, especially the precompiled test. On that
> machine you may very well have to bump up the timeout. We really just
> added the timeout to save our old CI server from freezing up solid if
> things went south.
>
> How long does the interpreted phase take? Precompiled can take as much
> as ten times as long.
Timings are below:
run-junit-interpreted:
[echo] compile=OFF, jit.threshold=20, jit.max=-1,
objectspace=true threadpool=false reflection=false version=ruby1_8
[junit] Testsuite: org.jruby.test.ScriptTestSuite
[junit] Tests run: 78, Failures: 0, Errors: 0, Time elapsed: 241.034 sec
[junit]
[junit] Testsuite: org.jruby.test.BFTSTestSuite
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 12.248 sec
[junit]
[junit] Testsuite: org.jruby.test.JRubyTestSuite
[junit] Tests run: 83, Failures: 0, Errors: 0, Time elapsed: 1,376.102 sec
[junit]
[junit] Testsuite: org.jruby.test.MRITestSuite
[junit] Tests run: 44, Failures: 0, Errors: 0, Time elapsed: 86.741 sec
[junit]
[junit] Testsuite: org.jruby.test.RubiconTestSuite
So, it's about a half-hour for what it gets done, and then I don't
know how long it took rubicon to time out. Is disabling the timeout a
simple thing? I'd be happy to time the test run on my computer, and
see if it can run often enough to be useful. I also have six more
ultra2's, so we could still get a CI build every hour (pipelining is
fun!). I'm not sure about what that would do to my electricity bill
though...
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
