Hi, check out the test comited in fff6b491e07d, it tests a fallback in unroll.py that we dont realy want to ocure by injecting an extra optimization stage that generates the issue we want to avoid.
On Fri, Jan 13, 2012 at 6:54 PM, Armin Rigo <[email protected]> wrote: > Hi, > > On Fri, Jan 13, 2012 at 13:01, Carl Friedrich Bolz <[email protected]> wrote: >> Yes, this breaks Pyrolog. That's fine, I can probably just increase the >> number. Could you write a test for this commit, though? > > It's a bit hard... I don't have a good enough understanding of the > reason for which we get cancellations. But I fear that we're going to > get the following: even if we manage to reproduce the issue in a test, > the next step will be "ah, but in this case we should obviously do > this or that instead of failing 4 times in a row". Then we do it. > And then the test is no longer a test for the original commit... > > > A bientôt, > > Armin. > _______________________________________________ > pypy-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pypy-dev -- Håkan Ardö _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
