| Summary: | dev-python/cliff-2.12.0-r1 tests hang | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
| Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | jstein, leio, python |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=665746 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | dev-python:cliff-2.12.0-r1:20180912-173002.log | ||
|
Description
Jonathan Lovelace
2018-09-13 00:17:37 UTC
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fcd055989bdc2d56e9abf094b8bc7a8fbeac031f commit fcd055989bdc2d56e9abf094b8bc7a8fbeac031f Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2018-09-14 19:47:36 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2018-09-14 19:47:36 +0000 dev-python/cliff: fix missing stestr dep Fixes: https://bugs.gentoo.org/666112 Fixes: https://bugs.gentoo.org/665746 Package-Manager: Portage-2.3.48, Repoman-2.3.10 dev-python/cliff/{cliff-2.12.0-r1.ebuild => cliff-2.12.0-r2.ebuild} | 1 + 1 file changed, 1 insertion(+) I've now installed =dev-python/cliff-2.12.0-r2 with tests temporarily masked, upgraded to =dev-python/stestr-2.1.0, and tried rebuilding dev-python/cliff with tests turned back on, and I see the same hanging behavior as with the earlier stestr version. From what I read in the stestr manual about how it stores data in "repositories," perhaps the "stestr init" command should be executed only once per build instead of once per Python implementation, or a separate repository should be set up per Python implementation using the --repo-url flag? I've just run into this again (with 2.12.0-r2), and when I ran 'ps -af' in another terminal I noticed an "xclip -selection c" process outside, but in the same terminal as, the sandbox process-tree. When I killed it, the build advanced, then apparently hung again; another 'ps -af' revealed another "xclip -selection c" process. When I killed that process, the tests and the rest of the build completed "successfully". Since the string "xclip" doesn't appear anywhere in the dev-python/cliff unpacked sources, nor in the files installed by stestr, I did some digging, and found that it is used by dev-python/pyperclip; based on what I found in https://github.com/asweigart/pyperclip/issues/116 and https://github.com/asweigart/pyperclip/pull/117 , if I had x11-misc/xsel installed it might well use that instead of xclip and not hang. Closing bugs reported for old versions, no longer in ::gentoo. Please reopen if you can still reproduce. |
