Generally, before releases it is a good idea to run the standard library unit tests. But testing those introduces the problem that bugs in the merge point of the cpython source branch for the stackless branch, will appear as bugs in the continuous integration.
Or something. On 9/4/14, Austin Bingham <[email protected]> wrote: > Hi all, > > I'm (slowly) making progress on continuous integration for stackless. > Before I get too much further, I wanted to make sure I'm setting up the > system we want. > > Basically the system will detect whenever there's a commit to the bitbucket > repository. It will then get those changes, build everything at that new > commit, and run the tests. The build will only succeed if everything builds > and all tests pass. Does this sound correct? > > Assuming that's all fine, can someone verify that these are right commands: > > hg clone https://bitbucket.org/stackless-dev/stackless > # or perhaps just hg pull > cd stackless > ./configure --enable-framework=$INSTALL_DIR --prefix=$INSTALL_DIR > make > $INSTALL_DIR/bin/python Stackless/unittests/runAll.py > > Anything missing? > > Austin > _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
