New issue 1918: Invalid entries in PyPy STM log
https://bitbucket.org/pypy/pypy/issue/1918/invalid-entries-in-pypy-stm-log
Konstantin Lopuhin:
How to reproduce (similar setup to #1917):
```
hg clone ssh://h...@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>
sys.exit(main(sys.argv[1:]))
File "/usr/local/bin/print_stm_log.py", line 190, in main
dump(parse_log(argv[0]))
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.
_______________________________________________
pypy-issue mailing list
pypy-issue@python.org
https://mail.python.org/mailman/listinfo/pypy-issue
