Thanks for the link. Setting up a continuous integration build should not, in principle, be much of a problem. It turns out that travis doesn't directly work with bitbucket, only github, so we'll need to find an alternative. These include:
1. A different hosted CI system that supports building C programs and works with bitbucket, e.g. perhaps drone.io. This is what I'll try first. 2. Mirroring the bitbucket repo in github via hg-git and using travis. This feels clunky, but maybe it'll work better than I expect. 3. Set up a dedicated Jenkins server to do the building and testing for each commit. This isn't very difficult, but we'd need an internet-facing machine to host it. Perhaps a cheap cloud machine somewhere...I'm open to suggestions. Our hand may ultimately be forced a bit by stackless-testsuite. I'm not sure how travis, drone, etc. will work with multiple interacting repos. It may be as easy as invoking a clone and build for stackless-test in the stackless CI script. I've never tried it. I know it can work with Jenkins. In any event, that's my plan right now. Any other ideas are welcome, of course. I'll work on this as I have time. Austin On Tue, Aug 5, 2014 at 10:19 PM, Richard Tew <richard.m....@gmail.com> wrote: > Easy mistake to make. > > See the following link for information about the stackless-testsuite > project. It slightly predates your joining the list. > > http://www.stackless.com/pipermail/stackless/2014-July/006393.html > > Looking forward to seeing what you come up with, as it sounds like > something we've long needed. There were vague ideas that CCP might be > able to provide something similar at one point, but CCP no longer > employs any Stackless Python developers and is I assume after 13 years > of Stackless support is moving on. > > Cheers, > Richard. > > On 8/5/14, Austin Bingham <austin.bing...@gmail.com> wrote: > > Ah, ok, I was on the completely wrong track. I had cloned > > "stackless-testsuite" from the bitbucket page and was trying to run that. > > Thanks for pointing me in the right direction. > > > > On that topic, though, what is stackless-testsuite for? It looks to be > very > > new, so is it perhaps the future home of the stackless tests? > > > > Austin > > > > > > On Mon, Aug 4, 2014 at 10:53 PM, Richard Tew <richard.m....@gmail.com> > > wrote: > > > >> Tests are normally run via Stackless\unittests\runAll.py > >> > >> The tests should work fine in 3.x, as we run them everytime we do a > >> release. The exception is 3.4, which requires updates to get > >> Stackless to work with it still. > >> > >> Cheers, > >> Richard. > >> > >> On 8/5/14, Austin Bingham <austin.bing...@gmail.com> wrote: > >> > Hi all, > >> > > >> > I met Anselm and Christian at EuroPython, and I sort of hinted that > I'd > >> be > >> > happy to set up Travis (or some other similar tool) to run the > >> > stackless > >> > tests on each commit. To that end, I've built stackless from source, > >> > but > >> > I'm having mixed luck running the tests. So I've got a few questions. > >> > > >> > First, are the tests supposed to work with Python 3? The tests > >> > explicitly > >> > access the __builtin__ module, which is not AFAIK supported in Python > >> > 3. > >> It > >> > doesn't look like there's any attempt to support both version, but I > >> > thought I'd check. > >> > > >> > Second, what's the proper/expected way of running the tests? Standard > >> > unittest discovery (i.e. python -m unittest discover) seems to work > >> > fine, > >> > though nose is picking up more than it probably should (e.g. functions > >> like > >> > create_type_tests_for_module()). How should I be executing the tests? > >> > > >> > Thanks for any help on this. > >> > > >> > Austin > >> > > >> > >> _______________________________________________ > >> Stackless mailing list > >> Stackless@stackless.com > >> http://www.stackless.com/mailman/listinfo/stackless > >> > > > > _______________________________________________ > Stackless mailing list > Stackless@stackless.com > http://www.stackless.com/mailman/listinfo/stackless >
_______________________________________________ Stackless mailing list Stackless@stackless.com http://www.stackless.com/mailman/listinfo/stackless
