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 branch results in the build slots being hogged for hours, >>> making the continuous development a lot less 'continuous'. We could >>> just decide to run the pyregr suite every so often, or whenever we >>> make an addition or change that could actually affect Python code (if >>> one updates a test then there is no use in running pyregr for >>> instance). >> >> +1 to manual + periodic for these tests. Alternatively we could make >> them depend on each other, so at most one core is consumed. > > Ok, I'll set it up.
They are now triggered by the (nightly) CPython builds and the four configurations run sequentially (there's an option for that), starting with the C tests. I would recommend configuring your own pyregr test jobs (if you have any) for manual runs by disabling all of their triggers. Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
