emerge hang - I killed it
Thank you for your bug reports. Tickets will be assigned even faster, if you assign your own tickets directly as author. We prepared a JavaScript plugin [1] for greasemonkey [2] which makes this very fast and easy. [1] https://github.com/mgorny/bug-assign-user-js [2] https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/
FEATURES=test causes "make test" to execute the shipped test.pl, which is interactive (expects input), so emerge hangs. The script however doesn't do a lot, it simply allows a tester to evaluate perl expressions manually. Two possible solutions: 1. set RESTRICT="test" for that ebuild so tests are skipped by emerge 2. setting the "AUTOMATED_TESTING=1" env variable so tests are skipped by test.pl
Created attachment 498394 [details] Term-ReadLine-TTYtter-1.4.ebuild, set AUTOMATED_TESTING variable to skip tests
Created attachment 498396 [details] Term-ReadLine-TTYtter-1.4.ebuild same thing, don't need the 'export' actually
*** Bug 623132 has been marked as a duplicate of this bug. ***
Sorry for the delay: Perl team would prefer it if there was some mechanism to coerce tests to be run in some regard, no matter how insignificant they may be. Hacks that simply *disable* tests aren't very useful. This is especially important given that without executing tests, there's no way to determine if a Perl module even has valid syntax, unlike C applications which at least have a safety net of a compile stage. I'm looking into this atm, and it seems there might be a way to redirect test input into the tests STDIN, which might make this work. At least then the test feature set, however arbitrarily simple, might provide some sort of useful coverage. NB: May require patching the tests to get some kind of useful reaction.
Created attachment 521340 [details, diff] Term-ReadLine-TTYtter-1.4-nointeractive.patch Attached is the patch I'd apply, which makes the test do *something* useful, and possibly trigger TTYtter codepaths. If the primary maintainer has no oppositions, I'll add it in an -r1 bump within the next 7 days. ( -r1 bump mostly for EAPI6ification ), and then purge the affected EAPI5 version 7 days after that.
Created attachment 521342 [details, diff] Term-ReadLine-TTYtter-1.4-nointeractive.patch Patch fixed to include input file.
Fine by me. Thanks.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=643430df185f46339d7eaa13933eb11fff76f57d commit 643430df185f46339d7eaa13933eb11fff76f57d Author: Kent Fredric <kentnl@gentoo.org> AuthorDate: 2018-03-03 02:40:04 +0000 Commit: Kent Fredric <kentnl@gentoo.org> CommitDate: 2018-03-03 02:40:52 +0000 dev-perl/Term-ReadLine-TTYtter: Fix interactive tests bug #624044 - EAPI6 - Tidy metadata.xml - Add upstream remote-id's - Patch out interactive tests while retaining some exectuable functionality testing - Normalize version Bug: https://bugs.gentoo.org/624044 Package-Manager: Portage-2.3.18, Repoman-2.3.6 .../Term-ReadLine-TTYtter-1.400.0-r1.ebuild | 18 +++++ .../Term-ReadLine-TTYtter-1.4-nointeractive.patch | 78 ++++++++++++++++++++++ dev-perl/Term-ReadLine-TTYtter/metadata.xml | 32 +++++---- 3 files changed, 116 insertions(+), 12 deletions(-)}
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f85dc0f20b89db0d0fef8273074662a564505f6d commit f85dc0f20b89db0d0fef8273074662a564505f6d Author: Kent Fredric <kentnl@gentoo.org> AuthorDate: 2018-03-13 12:05:33 +0000 Commit: Kent Fredric <kentnl@gentoo.org> CommitDate: 2018-03-13 12:05:48 +0000 dev-perl/Term-ReadLine-TTYtter: Cleanup old re bug #624044 Closes: https://bugs.gentoo.org/624044 Package-Manager: Portage-2.3.24, Repoman-2.3.6 .../Term-ReadLine-TTYtter-1.4.ebuild | 19 ------------------- 1 file changed, 19 deletions(-)