Hi, On Tue, Jan 21, 2014 at 1:21 AM, Aaron Meurer <[email protected]> wrote: > I take it you started working on this, because I just recieved a ton > of buildbot errors in my inbox today.
Yes, sorry, I should have warned you. I set up the windows binary builders to run every California morning: http://nipy.bic.berkeley.edu/builders/sympy-bdist32-27 http://nipy.bic.berkeley.edu/builders/sympy-bdist64-27 They run build the binary installer, install from the installer into a virtualenv, and then run the doctests and tests. The binaries end up here: http://nipy.bic.berkeley.edu/sympy-dist/ You can trigger builds for a specific revision (such as a tag) by entering the revision in the 'revision' box of the builder pages above. To do this, you'll need a password set up for the buildbots. I'm working on triggering build and tests for python 3.3 from the binary builds generated from 2.7, and then, being able to trigger builds via a script. Cheers, Matthew -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
