Trying to let my test-parallelization work have a shorter long pole to gate timing. But this, although the longest test suite, seems not to make as drastic a difference as I'd expected---I have to work how to reduce the infrastructure overhead more. (@GWTC, even if successful, this is unlikely to help most external users, unless you happen to have an extra hundred machines available for a test run. Sorry. It should, however, let us break you less often, if only by shortening the build/test cycle of the robot builder.)
On Tue, Oct 13, 2009 at 1:41 PM, <[email protected]> wrote: > What's the underlying motivation here? > > > http://gwt-code-reviews.appspot.com/77814/diff/1/2 > File user/test/com/google/gwt/user/DeRPCSuite.java (right): > > http://gwt-code-reviews.appspot.com/77814/diff/1/2#newcode16 > Line 16: package com.google.gwt.user; > Put this in gwt.rpc instead. > > http://gwt-code-reviews.appspot.com/77814/diff/1/2#newcode48 > Line 48: import com.google.gwt.user.server.Base64Test; > Fix imports. > > http://gwt-code-reviews.appspot.com/77814/diff/1/3 > File user/test/com/google/gwt/user/RPCSuite.java (right): > > http://gwt-code-reviews.appspot.com/77814/diff/1/3#newcode91 > Line 91: // moved to RpcValueSuite: > suite.addTestSuite(ValueTypesTest.class); > Are these comments part of the actual commit? > > > http://gwt-code-reviews.appspot.com/77814 > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
