Skip Menu |

This queue is for tickets about the Test-Warn CPAN distribution.

Report information
The Basics
Id: 37500
Status: resolved
Priority: 0/
Queue: Test-Warn

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

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: 0.11



Subject: Sub-Uplevel-0.19_03 Causes Test::Warn to fail
One tester using this module was getting test failures in one of my modules. When he revetted to 0.1901 the tests all pass. See: http://cpantesters.perl.org/show/XML-RSS-Tools.html#XML-RSS-Tools-0.31 Email conversation from my tester with the problems: Show quoted text
>>>>> On Mon, 7 Jul 2008 09:55:28 +0100, Dr Adam J Trickett
<adam.trickett@iredale.net> said: Show quoted text
ajt> Andreas, ajt> On Mon, 07 Jul 2008 at 08:08:40AM +0200, Andreas J. Koenig wrote:
Show quoted text
>> >>>>> On Sun, 6 Jul 2008 13:58:40 +0100, Dr Adam Trickett
<adam.trickett@iredale.net> said: Show quoted text
>>
>> > Could you possibly run the tests manually (Build and Make) to see
if there is Show quoted text
>> > any difference with your automated tests.
>> >> Interesting, I sent you three fails but I also sent you 5 passes. So >> it is nothing special for my testing box.
Show quoted text
ajt> Most peculiar.
Show quoted text
>> I just tried the fail 1831687 manually and could reproduce it.
Show quoted text
ajt> That's good, as long as it's reporiducable there is a chance it ajt> can be fixed. If I could reporduce it on one of my systems I'd be ajt> a lot happier, as I'll be able to fix it without disturbing you.
Show quoted text
>> I've now run out of time to further investigate, will continue in the >> (European) evening. Let me know if you have more concrete suggestions >> how to find out more.
Show quoted text
ajt> Thanks, I'll have a think and send you some ideas...
Found it: Sub-Uplevel-0.19_03 was the cause. Downgrading to 0.1901 let your tests pass. I found the same issue with the same three perls for Archive::Any which is also a user of Test::Warn. And then I looked at the dependencies of Test::Warn and Sub::Uplevel jumped into my eye because the error message contained the word "level". I wholeheartedly recommend that module writers add as many dependencies as they can get hold of to their listed dependencies. Including indirect dependencies. That way the test reports will contain better statistical data that can lead us to the culprit. In your case only instinct could help us. @David: Adam is the author of XML::RSS::Tools which use Test::Warn which FAILed on some of my perls due to Sub::Uplevel 0.19_03. I've replaced Sub::Uplevel in all my perls now. -- It's Not Magic, It's Work!
A recent change in Sub::Uplevel reveals a bug in how Test::Warn is using Sub::Uplevel. I'll move this to the Test::Warn queue and I'll coordinate fixes with the maintainer. -- David
On Mon Jul 07 16:52:14 2008, DAGOLDEN wrote: Show quoted text
> A recent change in Sub::Uplevel reveals a bug in how Test::Warn is using > Sub::Uplevel. > > I'll move this to the Test::Warn queue and I'll coordinate fixes with > the maintainer.
Has there been any progress on this bug? At quick glance, it looks that reducing both of Test::Warn's uplevel calls to `uplevel 1,$block` fixes the issue. - Alex
Втр. Окт. 21 15:07:47 2008, ALEXMV писал: Show quoted text
> On Mon Jul 07 16:52:14 2008, DAGOLDEN wrote:
> > A recent change in Sub::Uplevel reveals a bug in how Test::Warn is using > > Sub::Uplevel.
Show quoted text
> > Has there been any progress on this bug? At quick glance, it looks that > reducing both of Test::Warn's uplevel calls to `uplevel 1,$block` fixes > the issue.
Test::Warn 0.11 fixes this bug. -- Alexandr Ciornii, http://chorny.net