Skip Menu |

This queue is for tickets about the Log-Log4perl CPAN distribution.

Report information
The Basics
Id: 13110
Status: resolved
Priority: 0/
Queue: Log-Log4perl

People
Owner: MSCHILLI [...] cpan.org
Requestors: rrwo [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in:
  • 0.50
  • 0.51
  • 0.52
Fixed in: (no value)



Subject: Win32 and new PathTools 3.08 testing issues
It seems tests fail on Win32 because of confusion over slashes, for example: # Test 10 got: "t/003Layout.t-126 That's the message" (t/003Layout.t at line 128 ) # Expected: "t\\003Layout.t-126 That's the message" # t/003Layout.t line 128 is: ok($app->buffer(), File::Spec->catfile(qw(t 003Lay out.t)) .
[guest - Mon Jun 6 08:09:20 2005]: Show quoted text
> It seems tests fail on Win32 because of confusion over slashes, for > example: > # Test 10 got: "t/003Layout.t-126 That's the message" (t/003Layout.t > at line 128) > # Expected: "t\\003Layout.t-126 That's the message" > # t/003Layout.t line 128 is: ok($app->buffer(), File::Spec-
> >catfile(qw(t 003Lay
> out.t)) .
Interesting, it works on my Win32 (Activestate 5.8.6-811) installation. On your installation, it looks like Log::Log4perl does the right thing, using File::Spec->catfile() do arrive at the full path. There's two possible sources of error: (1) The test harness calls perl t/003Layout.t instead of perl t\003Layout.t (2) your Activestate perl's caller() function returns the filepath using "/" as the delimiter and not "\". Can you check which one it is? Thanks for your help. -- Mike
On Sun Jul 10 22:45:08 2005, MSCHILLI wrote: Show quoted text
> Can you check which one it is?
Haven't heard back, closing bug.
On Sun Jul 10 22:45:08 2005, MSCHILLI wrote: Show quoted text
> Can you check which one it is?
Haven't heard back, closing bug.