On 19 April 2011 12:53, Stefan Behnel <stefan...@behnel.de> wrote: > mark florisson, 19.04.2011 12:31: >> >> On 19 April 2011 12:19, Stefan Behnel wrote: >>> >>> mark florisson, 19.04.2011 11:14: >>>> >>>> Can I get a Hudson account so I can setup my branches there? >>> >>> I've created one for you. Please tell me when you have changed your >>> password, so that I can give you write access. >> >> Done. > > Ok, you should have write rights now. > > >>> Please be careful not to break too much, and note that it's easier to >>> work >>> at the file system level if you want to do mass duplication/adaptation of >>> jobs. If you tell me what you need, I can set it up for you. >> >> All I want is to run the master branch (it has the 'with gil' >> statement') and the openmp branch. I also want the fusedtypes branch, >> which I'll create in a minute or two. > > That's three branches in total, plus the builds in three CPython versions > (2.4, 2.7 and Py3k), plus 2xC/C++ testing each. So, at least 3+9+18=30 new > jobs that will compete with the others. > > I would expect that the three branches would rarely be changed all at the > same time (except when you update them from the main branch), but that may > still result in quite some additional delays due to the longer build queue.
Switching the branches would be fine with me, so 3 Python versions x 1 branch x 2xC/C++ = 6 jobs. Is it necessary to separate C from C++ testing? > Vitek currently has one set of build jobs for himself and can change the > branches at need. Question to the others: should we continue to do this, or > set up a full set of build jobs for each git branch we want to test? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel > _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
