| Summary: | dev-python/setuptools-7.0 fails tests with pypy3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | setuptools-7.0:20141120-121205.log.gz | ||
|
Description
Paolo Pedroni
2014-11-20 12:18:09 UTC
I am not able to reproduce this. sudo PYTHON_TARGETS=pypy3 ebuild setuptools-7.0.ebuild clean test ... Ran 126 tests in 11.578s OK (skipped=1) (In reply to Mike Gilbert from comment #1) > I am not able to reproduce this. > > sudo PYTHON_TARGETS=pypy3 ebuild setuptools-7.0.ebuild clean test > ... > Ran 126 tests in 11.578s > > OK (skipped=1) It _might_ be a problem with my pypy3. I'm in the process of recompiling it without lto (it takes a long time) and then I'll be back to you, hopefully in the early afternoon (Central European Time). (In reply to Mike Gilbert from comment #1) > I am not able to reproduce this. > > sudo PYTHON_TARGETS=pypy3 ebuild setuptools-7.0.ebuild clean test > ... > Ran 126 tests in 11.578s > > OK (skipped=1) I hate it when this happens (glad it's no a bug, though). Rebuilding dev-python/pypy3 without LTO fixed this. I'm going to revisit all the bugs I opened yesterday. Closing as INVALID |