[pypy-issue] Issue #1918: Invalid entries in PyPy STM log (pypy/pypy)

Konstantin Lopuhin issues-reply at bitbucket.org
Sat Nov 1 19:37:38 CET 2014

New issue 1918: Invalid entries in PyPy STM log

Konstantin Lopuhin:

How to reproduce (similar setup to #1917):

hg clone ssh://hg@bitbucket.org/kostialopuhin/tornado-stm-bench
cd tornado-stm-bench
hg up a038bf99de71
virtualenv env -p pypy-c-r74011-stm-jit
source env/bin/activate
pip install -r requirements.txt
PYPYSTM=stm.log ./primes.py 4

This will start a server on localhost:8888, then in another terminal (assuming you have siege installed):

./bench_primes.sh 10

And then, when trying to read stm.log

print_stm_log.py stm.log
$ print_stm_log.py stm.log
Traceback (most recent call last):
  File "app_main.py", line 75, in run_toplevel
  File "/usr/local/bin/print_stm_log.py", line 194, in <module>
  File "/usr/local/bin/print_stm_log.py", line 190, in main
  File "/usr/local/bin/print_stm_log.py", line 69, in parse_log
    raise ValueError("the file %r appears corrupted")
ValueError: the file %r appears corrupted

Although only a tiny fraction of log entries are corrupted.

More information about the pypy-issue mailing list