Author: Armin Rigo <ar...@tunes.org> Branch: Changeset: r50481:b673742c84f1 Date: 2011-12-13 22:47 +0100 http://bitbucket.org/pypy/pypy/changeset/b673742c84f1/
Log: Found out why the test fails, and document it. diff --git a/pypy/module/pypyjit/test_pypy_c/test_generators.py b/pypy/module/pypyjit/test_pypy_c/test_generators.py --- a/pypy/module/pypyjit/test_pypy_c/test_generators.py +++ b/pypy/module/pypyjit/test_pypy_c/test_generators.py @@ -17,6 +17,13 @@ g() log = self.run(main, [500]) + # XXX XXX this test fails so far because of a detail that + # changed with jit-simplify-backendintf. We should try to + # think of a way to be more resistent against such details. + # The issue is that we now get one Tracing, then go back + # to the interpreter hoping to immediately run the JITted + # code; but instead, we Trace again, just because another + # counter was also about to reach its limit... loop, = log.loops_by_filename(self.filepath, is_entry_bridge='*') assert loop.match_by_id("generator", """ ... _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit