Probably not, if we want to test all the pull requests. But if we set up a system like what I was talking about where the server can server out tests, then I too can probably set up an old computer or two to do testing with. Old computers like this are actually not that hard to come by (indeed, as I said, you could also just run this on your personal computer when you're not using it), and doing it in a distributed fashion is much easier than having some server or cloud node or something, because it only has to have internet access. You don't have to have ssh access or anything (assuming you have local access to the device), and if someone's computer goes down for whatever reason, then it's no big deal; the rest will just take on the load. The only thing that has to be stable is the test report server, which is hosted on the app engine, so it should be very stable (and of course GitHub, which is obviously also very stable).
Right now, Stefan's script works only for his machine, if I were to run the same script, we would just get duplicate reports (unless we timed them to be offset or something). So we really need to get some poling mechanism implemented, and then I think that even with just the computers we have, we should be able to alleviate, if not eliminate, our testing problems. Aaron Meurer On Sat, Dec 3, 2011 at 8:13 AM, Matthew Rocklin <mrock...@gmail.com> wrote: > It looks like shining panda gives one hour per day free to foss projects. Is > this sufficient for our needs? Or rather, how much compute time would a nice > testing system require? > > On Sat, Dec 3, 2011 at 8:57 AM, Aaron Meurer <asmeu...@gmail.com> wrote: >> >> I went ahead and registered for the Shining Panda thing, since it was >> free. There apparently is a waiting list for the free open source >> plan, and we are number 6. I'll let you know when it goes online. >> >> Aaron Meurer >> >> On Sat, Dec 3, 2011 at 7:53 AM, Aaron Meurer <asmeu...@gmail.com> wrote: >> > The biggest problem with Jenkins in my opinion is that it has such a >> > terrible user interface. >> > >> > SymPy-Bot is nice in that it allows completely distributed testing. >> > The script is so simple and self-contained that anyone can just clone >> > it and run it (I guess there are a few Python dependencies to install, >> > but we could probably make distribute do that work for us too if we >> > wanted). >> > >> > And testing pull requests is way more important than testing master; >> > this is attested to by the fact that we still have not implemented >> > master testing in sympy-bot. In some ways, testing pull requests >> > tests master as a side effect, because we always merge with master >> > first. In fact, the only time I run tests on master directly is when >> > doing a release, and even that's technically some branch. (Don't get >> > me wrong, though; testing master is important, and we should be doing >> > it). >> > >> > This is kind of analogous to the git/GitHub pull request model where >> > you review code before pushing it in and the >> > svn/<svn_review_tool_here> model, where you review it after it goes >> > in. It's pretty clear to me, and I think most others who use GitHub >> > pull requests, that the former is the superior way of doing things. >> > >> > Aaron Meurer >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To post to this group, send email to sympy@googlegroups.com. >> To unsubscribe from this group, send email to >> sympy+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/sympy?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to sympy@googlegroups.com. > To unsubscribe from this group, send email to > sympy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
