| Summary: | dev-python/fabric-1.10.2 bump / test failure | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | jlec |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | the build log | ||
|
Description
Patrick Lauer
2015-06-29 02:11:43 UTC
on running fabric-1.10.1.ebuild it yields Ran 392 tests in 104.171s FAILED (errors=2) 1 of those is; error: Socket is closed For this 1.10.2; AssertionError: '/bin/sh: fab: command not found' != 'Fatal error: It burns!\n\nAborting.' looks like the devs have decided to make '/bin/sh' find the file fab installed in the system. fab is the exec script installed to usr/bin; $ file /path/to/dev-python/fabric-1.10.1/image/usr/bin/fab : broken symbolic link to ../lib/python-exec/python-exec2 I am not sure if we have any have any viable way of setting up an installed state given the func distutils_install_for_testing has been declared all but useless from a number of sources. It appears there are some 'rogue' upstreams who write testsuites to run from an installed state. mb just restrict this testsuite or create a category of resolve TOOHARDBASKET which is an instance of WONTFIX Created attachment 424492 [details]
the build log
Already bumped ong ago |