[issue13990] Benchmarks: 2to3 failures on the py3 side

Francisco Martín Brugué added the comment: > So the tests failed but the benchmarks finished without issue? Yes. But the apparent diff is that I've used 2.6.8 If the benchmarks run without errors then I'm satisfied, else we figure out what this fails ever or we have a already translated copy ke

[issue13990] Benchmarks: 2to3 failures on the py3 side

Brett Cannon added the comment: So the tests failed but the benchmarks finished without issue? I'm not too worried about the tests since they are almost all str/bytes interaction issues (although I don't get the .decode() failure). If the benchmarks run without errors then I'm satisfied, else

[issue13990] Benchmarks: 2to3 failures on the py3 side

Francisco Martín Brugué added the comment: The box is a debian (wheezy): ci@random:~/Prog/cpython/benchmarks/py2$ uname -a Linux random 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux The source repository dir: ci@random:~/Prog/cpython/benchmarks/py2$ dir lib LICENSE.txt mak

[issue13990] Benchmarks: 2to3 failures on the py3 side

Brett Cannon added the comment: Can you copy-and-paste the exact commands you are using to build and run the benchmarks (along with version info for the interpreter used to do the building) as I'm on the same revision and can't reproduce anymore? $ mkdir benchmarks_py3k $ cd benchmarks_py3k/ $

[issue13990] Benchmarks: 2to3 failures on the py3 side

Francisco Martín Brugué added the comment: The actual tip for me is: ci@random:~/Prog/cpython/benchmarks/py2$ hg tip changeset: 164:61768f86170c tag: tip user:Brett Cannon date:Fri Aug 31 18:58:24 2012 -0400 summary: Allow for the specification of a base directory

[issue13990] Benchmarks: 2to3 failures on the py3 side

Francisco Martín Brugué added the comment: Just info: I still can reproduce that. (It's maybe just something wrong with my setup?) -- Added file: http://bugs.python.org/file27183/testsResult.txt ___ Python tracker

[issue13990] Benchmarks: 2to3 failures on the py3 side

Brett Cannon added the comment: I can't reproduce the problem anymore. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ __

[issue13990] Benchmarks: 2to3 failures on the py3 side

Changes by Brett Cannon : -- assignee: benjamin.peterson -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue13990] Benchmarks: 2to3 failures on the py3 side

Brett Cannon added the comment: It's translating properly for me now as well (but on a different machine). I will give it another try when I get home to see if I can reproduce success on the machine that was failing for me previously. -- status: pending -> open ___

[issue13990] Benchmarks: 2to3 failures on the py3 side

Changes by Ezio Melotti : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13990] Benchmarks: 2to3 failures on the py3 side

Antoine Pitrou added the comment: > Antoine (since you last looked at the benchmark suite for Python 3), do > you know anything about this? I don't know. It works here. It may depend on the version of 2to3 used for the conversion, try passing PYTHON=some_newer_python when running make_perf.sh

[issue13990] Benchmarks: 2to3 failures on the py3 side

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue13990] Benchmarks: 2to3 failures on the py3 side

Brett Cannon added the comment: It looks like 2to3 isn't being converted properly. Benjamin, is lib2to3 supposed to work on itself and result in a sane output? If not then the benchmark should probably drop its internal copy of lib2to3. Antoine (since you last looked at the benchmark suite fo

[issue13990] Benchmarks: 2to3 failures on the py3 side

New submission from Francisco Martín Brugué : Steps to reproduce: after following the usage instructions from make_perf3.sh go to the the py3 benchmarks directory and run the lib/2to3 tests (python3.2 test.py). The result are 3 failures and 17 errors. The equivalent procedure in the py2 benchma