| Summary: | dev-python/sqlalchemy-0.6.{1,3,4,7} fails tests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | phajdan.jr |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | [IR] | ||
| Package list: | Runtime testing required: | --- | |
|
Description
Patrick Lauer
2010-06-09 20:25:38 UTC
I can't reproduce this bug. Take an empty chroot, FEATURES="buildpkg" emerge -1 sqlalchemy; emerge -c; emerge --onlydeps -k sqlalchemy; emerge sqlalchemy That should trigger it And 0.6.3 does it too :) State the dev-python/nose version please... dev-python/nose-0.11.4 USE="test -doc -examples" After rebuilding sqlalchemy (0.6.3) into all my USE_PYTHON targets I no longer get this test fail. Patrick, try to: 1. rebuild sqlalchemy without running tests 2. rebuild sqlalchemy and run tests *** Bug 341391 has been marked as a duplicate of this bug. *** (In reply to comment #6) > After rebuilding sqlalchemy (0.6.3) into all my USE_PYTHON targets I no longer > get this test fail. > > Patrick, try to: > 1. rebuild sqlalchemy without running tests > 2. rebuild sqlalchemy and run tests Right, tests succeed if sqlalchemy is installed. And they still break if sqlalchemy is _not_ installed. This suggests a serious brokenness, like system sqlite being used instead of the built one or something similar. Could you test if this problem still occurs in dev-python/sqlalchemy-0.7.4 from Progress Overlay? (In reply to comment #9) > Could you test if this problem still occurs in dev-python/sqlalchemy-0.7.4 from > Progress Overlay? sqlalchemy-0.7.4 from _portage_ fixes the test failure for me. Should it get stabilized? Should be fixed in 0.7.4, now stabilizing in bug 404981. |