Skip Menu |

This queue is for tickets about the Encode CPAN distribution.

Report information
The Basics
Id: 96107
Status: open
Priority: 0/
Queue: Encode
People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)
Attachments
build.log

History Show all quoted text
  Sat May 31 20:01:25 2014 ether [...] cpan.org - Ticket created
Subject: 2.62 test failure
t/enc_utf8.t: failed to open 'f2' for reading: No such file or directory at t/enc_utf8.t line 42, <F> line 2. t/enc_utf8.t ............... Dubious, test returned 2 (wstat 512, 0x200)
  Wed Jun 25 17:21:48 2014 DANKOGAI [...] cpan.org - Correspondence added
On Sat May 31 20:01:25 2014, ETHER wrote: Show quoted text
> t/enc_utf8.t: failed to open 'f2' for reading: No such file or > directory at t/enc_utf8.t line 42, <F> line 2. > t/enc_utf8.t ............... > Dubious, test returned 2 (wstat 512, 0x200)
Too little hints. would you give me more data? Dan the Maintainer Thereof
  Wed Jun 25 17:21:48 2014 The RT System itself - Status changed from 'new' to 'open'
  Tue Jul 01 20:44:20 2014 ether [...] cpan.org - Correspondence added
On 2014-06-25 14:21:48, DANKOGAI wrote: Show quoted text
> On Sat May 31 20:01:25 2014, ETHER wrote:
> > t/enc_utf8.t: failed to open 'f2' for reading: No such file or > > directory at t/enc_utf8.t line 42, <F> line 2. > > t/enc_utf8.t ............... > > Dubious, test returned 2 (wstat 512, 0x200)
> > Too little hints. would you give me more data? > > Dan the Maintainer Thereof
Attached is the full build.log. Let me know if there's any system information I can look up for you.
Subject: build.log
Download build.log
application/octet-stream 30.8k

Message body not shown because it is not plain text.

  Wed Jul 02 03:26:32 2014 DANKOGAI [...] cpan.org - Correspondence added
Okay, you tried to install Encode via cpanm on perl which is installed via perlbrew. Which is strange because OS X is the very platform I am writing Encode upon, which is tested before shipped not only on OS X but also linuxes on travis... How did you invoke cpanm? Simply "cpanm Encode" or "perlbrew exec cpanm Encode"? If you have not tried the latter, would you do so and see what happens? Dan the Maintainer Thereof On Tue Jul 01 20:44:20 2014, ETHER wrote: Show quoted text
> On 2014-06-25 14:21:48, DANKOGAI wrote:
> > On Sat May 31 20:01:25 2014, ETHER wrote:
> > > t/enc_utf8.t: failed to open 'f2' for reading: No such file or > > > directory at t/enc_utf8.t line 42, <F> line 2. > > > t/enc_utf8.t ............... > > > Dubious, test returned 2 (wstat 512, 0x200)
> > > > Too little hints. would you give me more data? > > > > Dan the Maintainer Thereof
> > > Attached is the full build.log. Let me know if there's any system > information I can look up for you.
  Wed Jul 02 12:06:10 2014 ether [...] cpan.org - Correspondence added
Subject: Re: [rt.cpan.org #96107] 2.62 test failure
Date: Wed, 2 Jul 2014 09:05:56 -0700
To: Dan Kogai via RT <bug-Encode [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
On Wed, Jul 02, 2014 at 03:26:32AM -0400, Dan Kogai via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=96107 > > > Okay, you tried to install Encode via cpanm on perl which is installed via perlbrew. Which is strange because OS X is the very platform I am writing Encode upon, which is tested before shipped not only on OS X but also linuxes on travis... > > How did you invoke cpanm? Simply "cpanm Encode" or "perlbrew exec cpanm Encode"? If you have not tried the latter, would you do so and see what happens?
Yes, just 'cpanm Encode'. 'perlbrew exec cpanm Encode' attempts to run the command across all perlbrews, of which I have dozens... I think I found the answer though -- on this machine where tests fail, I have HARNESS_OPTIONS=j9. Are multiple tests using the same filenames for scratch files? This would cause tests to write over each other's data when run simultaneously -- so simply switching to using File::Temp::tempdir() in all tests should remedy this. Unfortunately, this variable isn't reported yet in CPAN::Reporter -- but we worked on this at the QA Hackathon in Lyon, and should be done soon -- https://github.com/cpan-testers/CPAN-Reporter/issues/14