New submission from Hugo <[email protected]>:

Pillow (the 'friendly' PIL fork) is tested on all Python versions available on 
Travis CI: Python 
2.6, 2.7, 3.2, 3.3, 3.4 and PyPy.

Since adding coverage using Coverage.py, we've been seeing intermittent 
segfaults on the PyPy 
build. Sometimes all tests will pass, sometimes one will fail, sometimes many 
will fail. You 
often get a different result re-running the same build.

For example: https://travis-ci.org/python-imaging/Pillow/jobs/25064994

```
running test_file_psd ...
=== error 35584
Segmentation fault
running test_file_tar ...
=== error 35584
Segmentation fault
running test_file_tiff ...
=== error 35584
Segmentation fault
```

A build with coverage enabled fails intermittently:
https://travis-ci.org/hugovk/Pillow/builds/25073481

A build with coverage removed passes:
https://travis-ci.org/hugovk/Pillow/builds/25073451

I re-ran it a few times with similar results.

Also, recording coverage makes the PyPy build job much slower, about x5.8 
slower. Coverage 
doesn't affect the Python 2.x or 3.x times much.

Covered build total: 28m38s
Non-covered build total: 21m22s
-
Covered PyPy job: 10m39s
Non-covered PyPy job: 3m50s
-
Covered Python 2.x and 3.x jobs (five jobs): 17m59s
Non-covered Python 2.x and 3.x jobs (five jobs): 17m32s
-
Covered selftest.py: 7.624s
Non-covered selftest.py: 2.860s
-
Covered Tests/run.py: 7m29.489s
Non-covered Tests/run.py: 1m17.394s

Travis CI says it's using PyPy 2.2.1:

```
python --version
Python 2.7.3 (87aa9de10f9c, Nov 24 2013, 18:48:13)
[PyPy 2.2.1 with GCC 4.6.3]
```

(Here's the issue at Pillow: 
https://github.com/python-imaging/Pillow/issues/640)

----------
messages: 6894
nosy: hugovk, pypy-issue
priority: bug
release: 2.2
status: unread
title: Intermittent segfaults with Coverage.py

________________________________________
PyPy bug tracker <[email protected]>
<https://bugs.pypy.org/issue1768>
________________________________________
_______________________________________________
pypy-issue mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-issue

Reply via email to