Skip Menu |

This queue is for tickets about the Module-Install CPAN distribution.

Report information
The Basics
Id: 61264
Status: resolved
Priority: 0/
Queue: Module-Install

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.00
Fixed in: 1.08



Subject: Tests hang on some perls
Among my smokers I have several perls for which the tests hang. I started debugging and found the processes hang in Admin.pm asking Show quoted text
>> 1. Module::Install::RPM >> 2. Module::Install::WriteAll >>Multiple extensions found for method 'WriteAll':
And there it sits. Note that it is NOT asking this on STDERR, so the output is never seen by a tester. The fact that the matrix shows so many PASS and hardly FAILs may be because all fails are just swallowed by harvesters for hanging jobs. Suggestions?
Subject: Re: [rt.cpan.org #61264] Tests hang on some perls
Date: Sat, 11 Sep 2010 14:31:29 +1000
To: bug-Module-Install [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
This is probably caused by Module::Install automatically loading any installed extensions. If any extension has some kind of critical bug, once installed it's quite probably going to screw over Module::Install. I'm current investigating the removal of this automated loading of all extensions. Adam K On 11 September 2010 13:44, Andreas Koenig via RT <bug-Module-Install@rt.cpan.org> wrote: Show quoted text
> Fri Sep 10 23:44:03 2010: Request 61264 was acted upon. > Transaction: Ticket created by ANDK >       Queue: Module-Install >     Subject: Tests hang on some perls >   Broken in: 1.00 >    Severity: Normal >       Owner: Nobody >  Requestors: ANDK@cpan.org >      Status: new >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=61264 > > > > Among my smokers I have several perls for which the tests hang. > > I started debugging and found the processes hang in Admin.pm asking >
>>>      1. Module::Install::RPM >>>      2. Module::Install::WriteAll >>>Multiple extensions found for method 'WriteAll':
> > And there it sits. Note that it is NOT asking this on STDERR, so the > output is never seen by a tester. The fact that the matrix shows so many > PASS and hardly FAILs may be because all fails are just swallowed by > harvesters for hanging jobs. > > Suggestions? > >
Closing as fixed in 1.08