Skip Menu |

This queue is for tickets about the CPAN CPAN distribution.

Report information
The Basics
Id: 43753
Status: open
Priority: 0/
Queue: CPAN
People
Owner: Nobody in particular
Requestors: wyant [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Unimportant
Broken in: 1.9304
Fixed in: (no value)
Attachments
31sessions.log
31sessions.patch
31sessions_nospace.log
31sessions_verbose.log

History Show all quoted text
  Sun Mar 01 15:19:20 2009 wyant [...] cpan.org - Ticket created
Subject: t/31sessions.t fails if build_dir contains a space.
Given the configuration Show quoted text
cpan> o conf build_dir
build_dir [/Users/tom/Library/Application Support/.cpan/build] t/31sessions.t fails test 'cmd[test CPAN::Test::Dummy::Perl5::Make::Features]'. The output of this script is attached. The test succeeds with Show quoted text
cpan> o conf build_dir /Users/tom/.cpan/build
Yes, I installed CPAN 1.9304 with build_dir set to '/Users/tom/.cpan/build', successfully installed, and then set build_dir back to '/Users/tom/Library/Application Support/.cpan/build', and the test still failed. The attached output is from this test. Unfortunately the testing mechanism is opaque enough to me that I have not been able to run this to earth. I will be glad to provide any additional information I can, though you may need to tell me where to look. Configuration: CPAN: 1.9304 Perl: 5.010 uname -a: Darwin white2 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 Thank you very much for your time and trouble.
  Mon Mar 02 00:13:58 2009 ANDK [...] cpan.org - Correspondence added
Cannot reproduce and cannot explain. During testing the build_dir in your private configuration is usually ignored and build_dir is set to `pwd`/t/dot-cpan/build. Why this does not happen for you is beyond my imagination. I think you did not attach anything or it got lost. You can edit the test script and turn on $VERBOSE somewhere around line 285. Maybe the output gives me a clue. Looking forward to tracking this, thanks for your support.
  Mon Mar 02 00:13:58 2009 The RT System itself - Status changed from 'new' to 'open'
  Mon Mar 02 10:22:28 2009 wyant [...] cpan.org - Correspondence added
On Mon Mar 02 00:13:58 2009, ANDK wrote: Show quoted text
> Cannot reproduce and cannot explain. During testing the build_dir in > your private configuration is usually ignored and build_dir is set to > `pwd`/t/dot-cpan/build. > > Why this does not happen for you is beyond my imagination. > > I think you did not attach anything or it got lost.
Well, it will not be the first time I have said I was going to attach something and then didn't. My apologies. Show quoted text
> > You can edit the test script and turn on $VERBOSE somewhere around line > 285. Maybe the output gives me a clue.
I did the current round of testing outside CPAN, since it sounds like this may not be as straightforward as I first hoped. I have done my darndest to attach four files, and I'm reading the names from the RT web page now, so that (hopefully) the chance for a screw-up on my part is minimalized. They are: 31sessions_verbose.log: This is the output from t/31sessions.t as modified by the also-attached (I hope!) 31sessions.patch, and run from directory '/Users/tom/Code/perl/CPAN Test/CPAN-1.9304'. $VERBOSE was true for _ALL_ tests, and I also uncommented the line that prints the $system used. 31sessions.log: This is the output from t/31sessions.t with $VERBOSE set to 1 only for the failing test, and run from directory '/Users/tom/Code/perl/CPAN Test/CPAN-1.9304'. 31sessions_nospace.log: This is the output from t/31sessions.t with $VERBOSE set to 1 only for the failing test, and run from directory '/Users/tom/Code/perl/CPAN_Test/CPAN-1.9304' (note replacement of space by underscore). 31sessions.patch: This is a unified diff between the original and modified t/31sessions.t. It is included so you can sanity-check my modifications. Show quoted text
> > Looking forward to tracking this, thanks for your support.
Thank you so much for your prompt response, and your willingness to dig into something that may turn out to be a pathological system on my end, given your failure to reproduce the problem. Tom Wyant
Download 31sessions_verbose.log
application/octet-stream 96.8k

Message body not shown because it is not plain text.

Download 31sessions.log
application/octet-stream 11.8k

Message body not shown because it is not plain text.

Download 31sessions_nospace.log
application/octet-stream 12.7k

Message body not shown because it is not plain text.

--- t/31sessions.old 2009-01-11 15:13:01.000000000 -0500 +++ t/31sessions.t 2009-03-02 09:50:39.000000000 -0500 @@ -277,7 +277,7 @@ for my $si (0..$#SESSIONS) { my $session = $SESSIONS[$si]; my $system = $session->{system} || $default_system; - # warn "# DEBUG: name[$session->{name}]system[$system]"; + warn "# DEBUG: name[$session->{name}]system[$system]"; ok($session->{name}, "opening new session $session->{name}"); open SYSTEM, "| $system 2> $devnull" or die "Could not open '| $system': $!"; for (my $i = 0; 2*$i < $#{$session->{pairs}}; $i++) { @@ -295,6 +295,8 @@ my($expect) = $session->{pairs}[2*$i+1]; my($actual) = $chunks[$i+1]; $actual =~ s{t\\00}{t/00}g if ($^O eq 'MSWin32'); + # $VERBOSE = $command eq 'test CPAN::Test::Dummy::Perl5::Make::Features'; + $VERBOSE = 1; diag("cmd[$command]expect[$expect]actual[$actual]") if $VERBOSE; my $success = like($actual,"/$expect/","cmd[$command]"); if (!$success) {