tsuraan wrote:
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...
Search for timeout in build.xml and just delete those attributes; it should run as long as necessary then.
Looks like it will probably be too slow to run the full test-all, you might be waiting for many, many hours. But getting a run going on interpreted or jit mode would be worthwhile.
- Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
