On 7/20/12 2:13 AM, Keshav Kini wrote: > Anne Schilling <a...@math.ucdavis.edu> writes: >> Here are several *ideas*: >> >> * We should run daily tests on the "needs review" section and pop patches >> off that section if the tests do not pass (or people are not actively >> working >> on making them pass). > > We could modify the Sage Patchbot ( http://patchbot.sagemath.org/ ) to > test the Combinat queue automatically. Or you could just have a > metaticket on trac and write a script that uploads patches from the > queue to the ticket and keeps posting comments like "apply a.patch > b.patch c.patch d.patch ... z.patch" on the ticket whenever the queue > changes, which will make the patchbot test the queue without the need > for any changes to the patchbot's code.
That sounds like a good idea. I would also like to have a computer set-up (like the new upcoming combinat.sagemath.org) with sage + sage-combinat queue installed. On this machine we could run the tests on the patches under "needing review" automatically. Right now I have to install sage and the sage-combinat queue by hand on boxen to run research code, which is a little cumbersome. Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
