On Jun 8, 9:15 pm, Ondrej Certik <[email protected]> wrote: > Hi Vinzent, > > On Sat, Jun 6, 2009 at 7:57 AM, Vinzent > > Steinberg<[email protected]> wrote: > > > What about a git hook that runs all tests affected by a change before > > committing? See for example > > >http://github.com/Arora/arora/blob/ca6cf65947ca10ace90291efa6b7160c9b... > > I think that we should not have things obstructing when we push things > in. Imagine the current git repo is broken and you have a fix, but for > some reason the above tests fails, then it will be real pain to get > things in. Not mentioning that the buildbots are not 100% bullet proof > either, it happened already couple times that they failed (it looked > like if the kernel just killed the testing process), but when I told > them to rebuild again, it worked.
There could be an option to force the push in case of emergency. Usually you just don't want to break tests. > > What we should have however is some way to run all the tests on the > test farm for any commit (not necessarily related to the master > branch). So that you can easily test if some change will break things > or not. If you (or anyone else!) would like to implement that, I'll > create you an account on the server. We could also offer a stable branch that mirrors master only if no test fails. Vinzent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
