You don't have to write code to compare against multiple runs. That's a lot more complicated.
Aaron Meurer On Sun, Aug 4, 2013 at 5:34 PM, Joachim Durchholz <j...@durchholz.org> wrote: > I was thinking along the lines of adding a few more options just to output > what tests aren't in order. > Having the speed of all tests would be great and that was indeed my > knee-jerk reaction, but that would mean keeping a history of previous > timings (we can't reuse timings across machines after all). And I thought > managing such a database is a bit too much to do in my spare time... > > However, I'm seeing something easier that could be done: > > - Within a run, keep track of all tests, their running time, and whether > they were marked @Slow or not. This information could be saved to disk for > comparison against future tests, but for now, it's just a list of timings > inside Python. > - Output all tests that are in the range between the fastest test marked > @Slow, and the slowest test not marked @Slow. Tests in this range are > candidates for relabelling. (Maybe reduce the range by 10% at each end to > account for noise.) > > This would obviously require a mode that runs both fast and @Slow tests. > > > -- > 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 sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
