$VAR2 = undef; # Failed test 'pipeline with embedded error' # at t/04-pipeline.t line 42. # Compared $data->[1][1] # got : 'ERR unknown command `OOPS`, with args beginning with: ' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-libressl_test-20190718-142211 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy (fallback) emerge -qpvO dev-perl/Redis [ebuild N ] dev-perl/Redis-1.991.0 USE="test -minimal"
Created attachment 584362 [details] emerge-info.txt
Created attachment 584364 [details] dev-perl:Redis-1.991.0:20190724-021808.log.bz2
Created attachment 584366 [details] emerge-history.txt
Created attachment 584368 [details] environment
Created attachment 584370 [details] etc.portage.tbz2
Created attachment 584372 [details] temp.tbz2
Created attachment 584374 [details] tests.tbz2
Don't try to use that log as-is. When decompressed, its just megabytes of "a" and will make "less" choke trying to linewrap. # bzip2 -d attach.bz2 katipo2 /tmp # du -sh attach 19M attach # sed 's/aaaa//g' attach > attach.fix katipo2 /tmp # du -sh attach.fix 3.0M attach.fix
Comment on attachment 584364 [details] dev-perl:Redis-1.991.0:20190724-021808.log.bz2 Actually, gonna mark it obsolete because that build log is full of hugely self-similar data that makes it impossible to read and find anomalies in. Something is making the build log far too verbose, far more verbose than you see testing the same thing on CPAN. CF: https://www.cpantesters.org/cpan/report/885f3a58-787c-11e9-819a-ec0a43e9d5c6 A more brief build log should be provided if at all.
https://metacpan.org/changes/release/DAMS/Redis-1.995#L13 # Failed test 'pipeline with embedded error' # at t/04-pipeline.t line 42. # Compared $data->[1][1] # got : 'ERR unknown command `OOPS`, with args beginning with: ' # expect : 'ERR unknown command 'OOPS'' # Looks like you failed 1 test of 11. t/04-pipeline.t ...........
(In reply to Kent Fredric (IRC: kent\n) from comment #9) > Comment on attachment 584364 [details] > dev-perl:Redis-1.991.0:20190724-021808.log.bz2 > > Actually, gonna mark it obsolete because that build log is full of hugely > self-similar data that makes it impossible to read and find anomalies in. > > Something is making the build log far too verbose, far more verbose than you > see testing the same thing on CPAN. > > CF: > https://www.cpantesters.org/cpan/report/885f3a58-787c-11e9-819a-ec0a43e9d5c6 > > A more brief build log should be provided if at all. Ugh. This is partly my fault trying to get build output that doesn't just silently crap itself: https://github.com/PerlRedis/perl-redis/issues/127# But the output it produces is utterly ridiculous \o/ so. IDK.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5ff30bbfe826a3e8e39e2545fcd91017290fc5a9 commit 5ff30bbfe826a3e8e39e2545fcd91017290fc5a9 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2021-08-15 16:59:32 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2021-08-15 16:59:32 +0000 dev-perl/Redis: Remove old Closes: https://bugs.gentoo.org/690610 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> dev-perl/Redis/Manifest | 1 - dev-perl/Redis/Redis-1.991.0.ebuild | 72 ------------------------------------- 2 files changed, 73 deletions(-)
