Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> We can drop support for 3.3 of course, but that's a separate discussion. +1 since 3.3 wasn’t ever part of any LTS distribution. 3.4 will live for a while but it’s also the first really good Python 3. :) ___ Twisted-Python mailing list Twisted-Python@

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 23, 2016, at 10:32 AM, Amber Hawkie Brown > wrote: > > However, since they now have funding to push it to 3.5, ... and can I just reiterate how SUPER PUMPED I am about this??? -g___ Twisted-Python mailing list Twisted-Python@twistedmatrix.c

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 23, 2016, at 10:27 AM, Mark Williams wrote: > > It appears that dropping Python 3.3 wouldn't exclude very many of our > users. 1/5 as many as Python 2.6, which we already don't support :). -glyph___ Twisted-Python mailing list Twisted-Python

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

The only reason to support Python 3.3 is PyPy3. However, since they now have funding to push it to 3.5, and PyPy3 is by no means production ready, I think it is reasonable to do this. I will announce the release after Twisted 16.4 as the final one to support Python 3.3, in accordance with our c

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

On Tue, Aug 23, 2016 at 09:44:16AM -0700, Glyph Lefkowitz wrote: > > We can drop support for 3.3 of course, but that's a separate discussion. I'm marginally in favor of it. I appreciate Adi's concern about the build infrastructure. And thanks to the inimitable Donald Stufft, it's easy to get a s

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 23, 2016, at 4:24 AM, Adi Roiban wrote: > > We now have 15 concurrent jobs for the next 10 days. > > Please check if it makes a difference worth more than $6000 per year :) > > Also, do we need both python 3.3 and 3.4 jobs? > > I think that we have non python 3.5 builders to prev

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

We now have 15 concurrent jobs for the next 10 days. Please check if it makes a difference worth more than $6000 per year :) Also, do we need both python 3.3 and 3.4 jobs? I think that we have non python 3.5 builders to prevent the usage of string formatting for bytes which is not available

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

PR for running only on trunk and release branches is here https://twistedmatrix.com/trac/ticket/8767 Travis-CI told that they can increase the limit to 15 jobs for one week so that we can give it a try. It would help to have the PR only build branch merged soon :) Cheers, Adi __

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 16, 2016, at 3:06 AM, Jean-Paul Calderone > wrote: > > On Mon, Aug 15, 2016 at 7:03 PM, Glyph Lefkowitz > wrote: > >> On Aug 15, 2016, at 2:11 PM, Jean-Paul Calderone > > wrote: >> >> On Mon, Aug 15, 2016 at 4:38 PM,

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

On Mon, Aug 15, 2016 at 7:03 PM, Glyph Lefkowitz wrote: > > On Aug 15, 2016, at 2:11 PM, Jean-Paul Calderone < > exar...@twistedmatrix.com> wrote: > > On Mon, Aug 15, 2016 at 4:38 PM, Glyph Lefkowitz > wrote: > > There's a lot that we can do to make Travis almost that fast, with > pre-built Dock

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 15, 2016, at 2:11 PM, Jean-Paul Calderone > wrote: > > On Mon, Aug 15, 2016 at 4:38 PM, Glyph Lefkowitz > wrote: > >>> There's a lot that we can do to make Travis almost that fast, with >>> pre-built Docker images and cached dependencies. We haven't

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

On Mon, Aug 15, 2016 at 4:38 PM, Glyph Lefkowitz wrote: There's a lot that we can do to make Travis almost that fast, with pre-built Docker images and cached dependencies. We haven't done much in the way of aggressive optimization yet. As recently discussed we're still doing twice as many build

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 15, 2016, at 6:06 AM, Adi Roiban wrote: > > On 15 August 2016 at 00:10, Glyph Lefkowitz wrote: >> >>> On Aug 14, 2016, at 3:38 AM, Adi Roiban wrote: >>> >>> Hi, >>> >>> We now have 5 concurrent jobs on Travis-CI for the whole Twisted >>> organization. >>> >>> If we want to reduce

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 15, 2016, at 3:55 AM, Jean-Paul Calderone > wrote: > > How might we guess this would compare to $6000/year development effort spent > towards speeding up the test suite? An excellent point :). Although both are somewhat moot if we don't do some fundraising... -glyph___

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

On 15 August 2016 at 00:10, Glyph Lefkowitz wrote: > >> On Aug 14, 2016, at 3:38 AM, Adi Roiban wrote: >> >> Hi, >> >> We now have 5 concurrent jobs on Travis-CI for the whole Twisted >> organization. >> >> If we want to reduce the waste of running push tests for a PR we >> should check that the

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

On Sun, Aug 14, 2016 at 7:10 PM, Glyph Lefkowitz wrote: > > > On Aug 14, 2016, at 3:38 AM, Adi Roiban wrote: > > > > If you think that we can raise $6000 per year for sponsoring our > > Travis-CI and that is worth increasing the queue size I can follow up > > with Travis-CI. > > I think that thi

Re: [Twisted-Python] Waiting time for tests running on Travis CI and Buildbot

> On Aug 14, 2016, at 3:38 AM, Adi Roiban wrote: > > Hi, > > We now have 5 concurrent jobs on Travis-CI for the whole Twisted organization. > > If we want to reduce the waste of running push tests for a PR we > should check that the other repos from the Twisted organization are > doing the sam