Another possibility is to run those tests in parallel, assuming that the build slave has more than one vCPU. Hopefully it does. I believe all the test servers and clients have a port option already, so we could be running up to 4 tests at a time and using all the CPU available (if there are 4 vCPUs). This would be a huge win for the cross test time for everyone.
James E. King, III Architect 8 Technology Drive, 2nd Floor Westborough, MA 01581-1756 Ph: 855-SVT-INFO -----Original Message----- From: Kyle Johnson [mailto:k...@powerworld.com] Sent: Wednesday, July 13, 2016 3:18 PM To: dev@thrift.apache.org Subject: Re: 0.10.0 I'm only a very minor contributor, but it seems that we ought to split out the tests for the cross builds before 0.10.0 release. Nothing is really fixed yet as we're straddling the 48/49 minute mark. If I have opportunity, I'll take a look at the cross builds and see about splitting up the tests because these failing Travis builds look really bad and effectively make the Travis hook useless as currently configured. Kyle Johnson PowerWorld Corporation 217-384-6330 x17 k...@powerworld.com http://www.powerworld.com On 7/13/16 2:00 PM, Jake Farrell wrote: > I'm going to add our Travis and AppVeyor badges to the README to make > it clear what the current state is to anyone looking to contribute, > I've also scripted out applying patches from a github pr to make it > easier for committers to be able to accept and close an issue, will > wrap into a new jira issue and get it in before looking at cutting the > 0.10.0 release candidate > > -Jake > > On Wed, Jul 13, 2016 at 2:03 PM, Roger Meier <ro...@bufferoverflow.ch> > wrote: > >> +1 we should ship more often >> >> -roger >> Quoting Randy Abernethy <r...@apache.org>: >> >> +1 >>> On Sun, Jul 10, 2016 at 7:02 PM, Jake Farrell <jfarr...@apache.org> >>> wrote: >>> >>> With the builds now solely on travis and the pre-commit green again >>> what >>>> are peoples thoughts on cutting 0.10.0, any objections? >>>> >>>> -Jake >>>> >>>> >> --------------------------------------------------------------------------------------- PRIVACY STATEMENT: This message is a PRIVATE communication. This message and all attachments are a private communication sent by SimpliVity and are considered to be confidential or protected by privilege. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. ---------------------------------------------------------------------------------------
