This queue is for tickets about the File-Path CPAN distribution.

Report information
The Basics
Id:
106304
Status:
resolved
Priority:
Low/Low
Queue:

People
Owner:
jkeenan [...] cpan.org
Requestors:
RICHE [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
(no value)
Broken in:
2.11
Fixed in:
(no value)



Subject: Dependency not identified by multithreaded blead build
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 405
See http://www.nntp.perl.org/group/perl.daily-build.reports/2015/08/msg180930.html File::Path is testing before Carp, which causes the build failure. ln 35425 of http://m-l.org/~perl/smoke/perl/win32/smoke-me/Karl%20Williamson/log55eb4084d561c28e746ac646230934efaced8327.log.gz shows the failure ln 36185 of the same file shows Carp being tested This may be a reflection of 'require Carp' in a sub
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-4151-1439040081-499.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 205
perl itself builds differently than CPAN modules. All of the core modules are available. The problem here is that the paths in @INC are relative, but the test is changing directories before loading Carp.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-4151-1439040081-499.106304-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org> <rt-4.0.18-4151-1439040081-499.106304-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-31079-1439041888-113.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 687
On Sat Aug 08 09:21:21 2015, haarg wrote:
Show quoted text
> perl itself builds differently than CPAN modules. All of the core > modules are available. > > The problem here is that the paths in @INC are relative, but the test > is changing directories before loading Carp.
Well, that is an awesome hint. I guess there's a few choices here. - Change how Carp is loaded (which I really don't want to touch) - Manipulate @INC to fq path in the test's BEGIN block (which I don't want to do because users could have relative @INC) - Change tests to not chdir ... but it changes a lot of test code - After each test block, change back to the original directory ... which probably is the best thing to do
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-31079-1439041888-113.106304-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org> <rt-4.0.18-4151-1439040081-499.106304-0-0@rt.cpan.org> <rt-4.0.18-31079-1439041888-113.106304-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-2775-1439043239-1078.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 721
On Sat Aug 08 09:51:28 2015, RICHE wrote:
Show quoted text
> On Sat Aug 08 09:21:21 2015, haarg wrote:
> > perl itself builds differently than CPAN modules. All of the core > > modules are available. > > > > The problem here is that the paths in @INC are relative, but the test > > is changing directories before loading Carp.
> > > Well, that is an awesome hint. I guess there's a few choices here. >
[snip]
Show quoted text
> - After each test block, change back to the original directory ... > which probably is the best thing to do
Without having looked at Path.t, my hunch is that that is indeed the best thing to do. Rich: If you want to split up the workload on these test modifications, just let me know. Thank you very much. Jim Keenan
MIME-Version: 1.0 (1.0)
X-Spam-Status: No, score=-5.9 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, FROM_OUR_RT=-4, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
In-Reply-To: <rt-4.0.18-2775-1439043239-1568.106304-5-0@rt.cpan.org>
X-Mailer: iPhone Mail (12H143)
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-106304@rt.cpan.org> <rt-4.0.18-31079-1439038251-959.106304-5-0@rt.cpan.org> <rt-4.0.18-4151-1439040081-499.106304-5-0@rt.cpan.org> <rt-4.0.18-31079-1439041888-113.106304-5-0@rt.cpan.org> <rt-4.0.18-2775-1439043239-1568.106304-5-0@rt.cpan.org>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
content-type: text/plain; charset="utf-8"
Message-ID: <1C1019DC-8EA9-4011-80C5-4F8B527BF969@richelberger.com>
X-RT-Original-Encoding: utf-8
X-Spam-Score: -5.9
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 37ACD2402E0 for <cpan-bug+file-path@hipster.bestpractical.com>; Sat, 8 Aug 2015 11:10:50 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFHZ2BqQyh8S for <cpan-bug+file-path@hipster.bestpractical.com>; Sat, 8 Aug 2015 11:10:49 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 4E7542402CF for <bug-file-path@rt.cpan.org>; Sat, 8 Aug 2015 11:10:47 -0400 (EDT)
Received: (qmail 20537 invoked by alias); 8 Aug 2015 15:10:46 -0000
Received: from p3plsmtpa11-02.prod.phx3.secureserver.net (HELO p3plsmtpa11-02.prod.phx3.secureserver.net) (68.178.252.103) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Sat, 08 Aug 2015 08:10:42 -0700
Received: from [30.85.122.180] ([172.56.3.113]) by p3plsmtpa11-02.prod.phx3.secureserver.net with id 2FAd1r0062SHwok01FAdMD; Sat, 08 Aug 2015 08:10:38 -0700
Delivered-To: cpan-bug+file-path@hipster.bestpractical.com
Subject: Re: [rt.cpan.org #106304] Dependency not identified by multithreaded blead build
Return-Path: <rich@richelberger.com>
X-Spam-Check-BY: la.mx.develooper.com
X-Original-To: cpan-bug+file-path@hipster.bestpractical.com
X-RT-Mail-Extension: file-path
Date: Sat, 8 Aug 2015 11:10:36 -0400
X-Spam-Level:
To: "bug-File-Path@rt.cpan.org" <bug-File-Path@rt.cpan.org>
Content-Transfer-Encoding: quoted-printable
From: Richard Elberger <rich@richelberger.com>
RT-Message-ID: <rt-4.0.18-27004-1439046651-978.106304-0-0@rt.cpan.org>
Content-Length: 1225
I can start on it this evening and will see if it starts to become a chore. But I think it will be pretty quick once the pattern is identified. I do need to figure an effective way of testing this though. It would be ideal to repro it outside of a full on Perl build. Sent from my iPhone
Show quoted text
> On Aug 8, 2015, at 10:13, James E Keenan via RT <bug-File-Path@rt.cpan.org> wrote: > > Queue: File-Path > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=106304 > >
>>> On Sat Aug 08 09:51:28 2015, RICHE wrote: >>> On Sat Aug 08 09:21:21 2015, haarg wrote: >>> perl itself builds differently than CPAN modules. All of the core >>> modules are available. >>> >>> The problem here is that the paths in @INC are relative, but the test >>> is changing directories before loading Carp.
>> >> >> Well, that is an awesome hint. I guess there's a few choices here.
> [snip] >
>> - After each test block, change back to the original directory ... >> which probably is the best thing to do
> > Without having looked at Path.t, my hunch is that that is indeed the best thing to do. Rich: If you want to split up the workload on these test modifications, just let me know. > > Thank you very much. > Jim Keenan > >
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-12168-1439252554-1180.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 447
Examining the chart summarizing Perl 5 smoke testing at develop.help.org, the first Win2000 smoke run which reports a failure in cpan/File-Path/t/Path.t is this one: http://www.nntp.perl.org/group/perl.daily-build.reports/2015/07/msg180327.html ... which, not surprisingly, is the first report on this OS after Chris Williams merged File-Path 2.11 into blead. http://perl5.git.perl.org/perl.git/commit/139271cd3e9cb3cf25072ebdd400e52275c61b96
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-12472-1489008305-1372.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1270
On Sat Aug 08 08:50:51 2015, RICHE wrote:
Show quoted text
> See > > http://www.nntp.perl.org/group/perl.daily- > build.reports/2015/08/msg180930.html > > File::Path is testing before Carp, which causes the build failure. > > ln 35425 of http://m-l.org/~perl/smoke/perl/win32/smoke- > me/Karl%20Williamson/log55eb4084d561c28e746ac646230934efaced8327.log.gz > shows the failure > > ln 36185 of the same file shows Carp being tested > > This may be a reflection of 'require Carp' in a sub
I *think* (but cannot prove) that this situation has cleared up. The problem was originally reported against CPAN version 2.11, but we have had 2.12 for a long time. When I go to matrix.cpantesters.org, I don't see any failures for File-Path 2.12_001 on MSWin32. See http://matrix.cpantesters.org/?dist=File-Path;os=mswin32;reports=1 which includes reports from testers who are usually quite reliable. I also don't see any failures for this test when it's run as part of smoke tests of Perl 5 blead -- but I have to qualify that by noting that at the present time we have only 1 steady source of smoke tests on Win32. See http://perl5.test-smoke.org/search and filter on 'MSWin32' for operating system. Rich, can you confirm that this has been resolved? Thank you very much. Jim Keenan
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-12472-1489008305-1372.106304-0-0@rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-31079-1439038251-959.0-0-0@rt.cpan.org> <rt-4.0.18-12472-1489008305-1372.106304-0-0@rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-3049-1496524102-1995.106304-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1515
On Wed Mar 08 16:25:05 2017, JKEENAN wrote:
Show quoted text
> On Sat Aug 08 08:50:51 2015, RICHE wrote:
> > See > > > > http://www.nntp.perl.org/group/perl.daily- > > build.reports/2015/08/msg180930.html > > > > File::Path is testing before Carp, which causes the build failure. > > > > ln 35425 of http://m-l.org/~perl/smoke/perl/win32/smoke- > > me/Karl%20Williamson/log55eb4084d561c28e746ac646230934efaced8327.log.gz > > shows the failure > > > > ln 36185 of the same file shows Carp being tested > > > > This may be a reflection of 'require Carp' in a sub
> > I *think* (but cannot prove) that this situation has cleared up. The > problem was originally reported against CPAN version 2.11, but we have > had 2.12 for a long time. When I go to matrix.cpantesters.org, I > don't see any failures for File-Path 2.12_001 on MSWin32. See > http://matrix.cpantesters.org/?dist=File-Path;os=mswin32;reports=1 > which includes reports from testers who are usually quite reliable. > > I also don't see any failures for this test when it's run as part of > smoke tests of Perl 5 blead -- but I have to qualify that by noting > that at the present time we have only 1 steady source of smoke tests > on Win32. See http://perl5.test-smoke.org/search and filter on > 'MSWin32' for operating system. > > Rich, can you confirm that this has been resolved? > > Thank you very much. > Jim Keenan
File-Path 2.13's CPANtesters reports on Win32 are all green so far, so I am marking this ticket Resolved. Thank you very much. Jim Keenan


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.