Stefan Behnel, 13.04.2012 07:11:
> Robert Bradshaw, 12.04.2012 22:21:
>> On Thu, Apr 12, 2012 at 11:21 AM, mark florisson wrote:
>>> Could we run the pyregr test suite manually instead of automatically?
>>> It takes a lot of resources to build, and a single simple push to the
>>> cython-devel branc
mark florisson, 12.04.2012 20:21:
> Could we run the pyregr test suite manually instead of automatically?
> It takes a lot of resources to build, and a single simple push to the
> cython-devel branch results in the build slots being hogged for hours,
Careful here. It takes a lot of time, yes, but
Robert Bradshaw, 12.04.2012 22:21:
> On Thu, Apr 12, 2012 at 11:21 AM, mark florisson wrote:
>> Could we run the pyregr test suite manually instead of automatically?
>> It takes a lot of resources to build, and a single simple push to the
>> cython-devel branch results in the build slots being hogg
On Thu, Apr 12, 2012 at 11:21 AM, mark florisson
wrote:
> Hey,
>
> Could we run the pyregr test suite manually instead of automatically?
> It takes a lot of resources to build, and a single simple push to the
> cython-devel branch results in the build slots being hogged for hours,
> making the con
Hey,
Could we run the pyregr test suite manually instead of automatically?
It takes a lot of resources to build, and a single simple push to the
cython-devel branch results in the build slots being hogged for hours,
making the continuous development a lot less 'continuous'. We could
just decide to
