On Wed, Oct 05, 2005 at 06:26:17PM -0400, David Golden wrote:
> Michael G Schwern wrote:
> >AFAIK there is only one module of consequence which does screen scraping
> >on Test::More and that's Test::Builder::Tester (Test::Warn, it turns out,
> >fails because of Test::Builder::Tester). Fix that,
AmethystSHEVEK
Apache-ACEProxy MIYAGAWA
Apache-DoCoMoProxy KOBAYASI
Apache-Gallery LEGART
Apache-No404Proxy MIYAGAWA
[...the long list of modules continues...]
This list came from CPANTS, right? I think there's something screwy
with the way it's following dependencies.
* Rolling back the change is a pain in my ass.
BTW, this shouldn't be true.
Just grab the previous stable tarball, unroll it, change the version to
a higher one, and release. If it's a bitch to backout that one path,
backout the entire stable release to the previous one.
It's 5 lines of cod
I'm disinclined to back this change out. See the bug for reasoning.
http://rt.cpan.org/NoAuth/Bug.html?id=14936
To sum up:
* There was ample warning.
* You shouldn't be relying on screen scraping.
* The fix to Test::Builder::Tester is trivial.
* Rolling back the change is a pain in my ass.
The
Just grab the previous stable tarball, unroll it, change the version to
a higher one, and release. If it's a bitch to backout that one path,
backout the entire stable release to the previous one.
Did you see the number of bug fixes between 0.60 and 0.61? No, I'm not
rolling back the entire re
AFAIK there is only one module of consequence which does screen scraping
on Test::More and that's Test::Builder::Tester (Test::Warn, it turns out,
fails because of Test::Builder::Tester). Fix that, upload a new version
and the problem goes away.
Which is not true at all. Test::More gets upgra
> Once Test-URI is upgraded, we are going to need to make sure the newest
> version is installed, so could the authors of the following modules
> please note you will need to do a new release to update this dependency.
>
> Amethyst SHEVEK
> Apache-ACEProxy MIYAGAWA
> Apache-DoCoMoProxy
On 10/5/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 05, 2005 at 11:22:40PM +1000, Adam Kennedy wrote:
> > Please ignore these bad reports. I've contacted Schwern to get that
> > specific change to Test::More backed out ASAP. These problem, if you get
> > any, should go away short
Some more test failures confirmations...
Test::Exception is uninstallable.
Test::SubCalls is uninstallable.
Test::Pod is uninstallable.
Test::Warn is uninstallable.
test_fail() which is the problem in TB::Tester was really only a
convenience function for test_diag( Failed at ... ).
Pretty
On Oct 5, 2005, at 11:38 AM, Michael G Schwern wrote:
I'm done talking about this until I see some attempt at fixing
Test::Builder::Tester. It could have been done by now.
I'll do it tomorrow unless someone else already has.
--- Joe M.
Michael G Schwern wrote:
AFAIK there is only one module of consequence which does screen scraping
on Test::More and that's Test::Builder::Tester (Test::Warn, it turns out,
fails because of Test::Builder::Tester). Fix that, upload a new version
and the problem goes away.
Nit: does Test::Harne
On Thu, Oct 06, 2005 at 03:39:59AM +1000, Adam Kennedy wrote:
> If we start with everything broken and try to gradually fix it, we're
> going to have little errors here and there for a long time.
AFAIK there is only one module of consequence which does screen scraping
on Test::More and that's Te
On Thu, Oct 06, 2005 at 03:43:50AM +1000, Adam Kennedy wrote:
> >>* Rolling back the change is a pain in my ass.
>
> BTW, this shouldn't be true.
It shouldn't because I should have long ago writen a routine to check my
diagnostics instead of hard coding it all over the tests.
> Just grab the pr
On Wed, Oct 05, 2005 at 11:22:40PM +1000, Adam Kennedy wrote:
> Please ignore these bad reports. I've contacted Schwern to get that
> specific change to Test::More backed out ASAP. These problem, if you get
> any, should go away shortly.
>
> Given that the repair alternatives are to backout the
The new version of Test::More from Sep 23rd improved the STDERR output
on test failure. Unfortunately, this has accidentally broken
Test::Builder::Tester's test_fail function. (and maybe other
test-testing modules)
http://rt.cpan.org/NoAuth/Bug.html?id=14936
T:B:Tester is used by about 26 oth
15 matches
Mail list logo