On Thu, Oct 06, 2005 at 10:08:22AM +0100, Fergal Daly wrote:
> > I'll consider putting in some more information into the
> > Test::Builder->details so information like the file and line number
> > where the test occured can be gotten without scraping.
> >
> > I'd really like to have this as well. C
On 10/5/05, Joe McMahon <[EMAIL PROTECTED]> wrote:
> From Schwern's comment:
>
> I'll consider putting in some more information into the
> Test::Builder->details so information like the file and line number
> where the test occured can be gotten without scraping.
>
> I'd really like to have this a
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
> 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
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
* 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
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.
From Schwern's comment:
I'll consider putting in some more information into the
Test::Builder->details so information like the file and line number
where the test occured can be gotten without scraping.
I'd really like to have this as well. Current projects could really use
it.
--- Joe M.
11 matches
Mail list logo
