| Summary: | dev-python/rply-0.7.2-r1 test phase broken | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mgorny |
| Priority: | Normal | Keywords: | TESTED, UPSTREAM |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/alex/rply/issues/26 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Patrick Lauer
2014-04-21 09:29:48 UTC
DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]
test? (
dev-python/py[${PYTHON_USEDEP}]
dev-python/pytest[${PYTHON_USEDEP}] )"
Don't you have some issue with USE=test?
(In reply to Michał Górny from comment #1) > DEPEND="dev-python/setuptools[${PYTHON_USEDEP}] > test? ( > dev-python/py[${PYTHON_USEDEP}] > dev-python/pytest[${PYTHON_USEDEP}] )" > > Don't you have some issue with USE=test? well whether yes or no, py3.3 does have issues with the suite. Two in fact; snipped; * python3_3: running distutils-r1_run_phase python_test ====================================================== test session starts ====================================================== platform linux -- Python 3.3.5 -- py-1.4.20 -- pytest-2.5.2 collected 35 items / 1 skipped tests/test_parsergenerator.py FF....... __ TestParserGenerator.test_simple _ > assert parser.lr_table.lr_action == [ {"VALUE": 2}, {"$end": 0}, {"$end": -1}, ] E assert [{'VALUE': 1}..., {'$end': 0}] == [{'VALUE': 2},... {'$end': -1}] E At index 0 diff: {'VALUE': 1} != {'VALUE': 2} __ TestParserGenerator.test_empty_production __ > assert parser.lr_table.lr_action == [ {"$end": -3, "VALUE": 3}, {"$end": 0}, {"$end": -1}, {"$end": -3, "VALUE": 3}, {"$end": -2}, ] E assert [{'$end': -3,... {'$end': -2}] == [{'$end': -3, ... {'$end': -2}] E At index 0 diff: {'VALUE': 1, '$end': -3} != {'VALUE': 3, '$end': -3} == 2 failed, 33 passed, 1 skipped in 0.38 seconds == ditto py3.4 run from both source and the ebuild. Its failures when run from the ebuild appear inconsistent; sometimes pass, sometimes fail 2. a very prompt reply from upstream; "I don't believe the test failures indicate a bug, although it would be nice to fix them, I'm not sure what that fix looks like." 24 Apr 2014; Ian Delaney <idella4@gentoo.org> rply-0.7.2-r1.ebuild: Excluding failed tests under py3 subsequent to upstream issue rply/issues/26, closes Bug #508308 *** Bug 507336 has been marked as a duplicate of this bug. *** |
