Comment #9 on issue 2863 by asmeu...@gmail.com: Plotting failures with SymPy-Bot
http://code.google.com/p/sympy/issues/detail?id=2863
I was able to bisect the change from one failure to the other (and yes, it took forever; I would recommend creating a scratch clone of sympy and doing it in the background from your other work), but I couldn't bisect the original change because I can only reproduce this in sympy-bot, and it merges the pull requests, which all include the first failures.
So could you bisect the original failure? I think that would help with debugging. If you're clever, you could even automate it with git bisect run and run it overnight.
And by the way, the reproducibility most likely has something to do with the state of your pyglet installation.
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-issues@googlegroups.com. To unsubscribe from this group, send email to sympy-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en.
