Skip Menu |
Report information
Id: 133627
Status: open
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors: marcus [at] breese.com
Cc:
AdminCc:

Operating System: (no value)
PatchStatus: (no value)
Severity: low
Type: unknown
Perl Version: (no value)
Fixed In: (no value)



To: perlbug [...] perl.org
From: Marcus Breese <marcus [...] breese.com>
Subject: Error in perlbug test while building
Date: Mon, 29 Oct 2018 12:47:42 -0400
Download (untitled) / with headers
text/plain 690b
Based on this patch/test: https://rt.perl.org/Public/Bug/Display.html?id=128020 I apologize for not filing this with perlbug, but this error was encountered while compiling a new version of Perl (5.28.0) and I didn't want to use an older installed version to submit the bug. When testing, the bug that was patched in the above link, is marked as a failure if the user's $PATH is longer than 1000 characters long. This is because the PATH variable doesn't contain any whitespace that can be used to easily split the line with Text::Wrap. I have not patch for this, but the workaround is to explicitly set the PATH to something shorter than 1000 characters when testing. -- Marcus Breese
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 1.1k
On Mon, 29 Oct 2018 16:48:24 GMT, marcus@breese.com wrote: Show quoted text
> Based on this patch/test: > https://rt.perl.org/Public/Bug/Display.html?id=128020 > > I apologize for not filing this with perlbug, but this error was > encountered while compiling a new version of Perl (5.28.0) and I > didn't want to use an older installed version to submit the bug. > > When testing, the bug that was patched in the above link, is marked as > a failure if the user's $PATH is longer than 1000 characters long. > This is because the PATH variable doesn't contain any whitespace that > can be used to easily split the line with Text::Wrap. > > I have not patch for this, but the workaround is to explicitly set the > PATH to something shorter than 1000 characters when testing. > > -- > Marcus Breese
Can you provide *as attachments* (rather than inline): * The output of the failing test file(s). For example: ##### cd t;./perl harness -v ../lib/perl5db.t 2>&1 | tee ../test_failure_output.txt; cd - ##### * The output of './perl -Ilib -V' from the perl you were compiling. That will assist us in identifying the problem. Thank you very much. -- James E Keenan (jkeenan@cpan.org)


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org