Michael G Schwern
2012-08-02 23:38:44 UTC
Moving along the trail of getting Test::Builder 1.5 ready (and CPAN ready for
Test::Builder 1.5), the next step is to fix the Test modules which are
failing. While they fail, large chunks of CPAN cannot be tested.
I've set up issues for the known failures. Some of them are probably very
easy, some are not so easy, and some are really involved.
https://github.com/schwern/test-more/issues?milestone=14&state=open
This is only round one. Once the known Test module failures are fixed, we can
re-smoke and test all the things that can't be tested because of dependency
failures. That would be all those "DISCARD"s here in the last smoke run.
https://github.com/schwern/test-more/issues/306
What's also very helpful is doing an analysis, figuring out why it's broken,
and posting that to the issue. It will make fixing it that much faster.
Also very important is figuring out if it's a problem with their test suite,
or if it's a problem with the module itself. If the module is broken,
Test::Builder 1.5 can declare that version in conflict and prevent upgrading
Test::Builder from breaking existing CPAN installations.
Of course, complete fixes are appreciated.
Test::Builder 1.5), the next step is to fix the Test modules which are
failing. While they fail, large chunks of CPAN cannot be tested.
I've set up issues for the known failures. Some of them are probably very
easy, some are not so easy, and some are really involved.
https://github.com/schwern/test-more/issues?milestone=14&state=open
This is only round one. Once the known Test module failures are fixed, we can
re-smoke and test all the things that can't be tested because of dependency
failures. That would be all those "DISCARD"s here in the last smoke run.
https://github.com/schwern/test-more/issues/306
What's also very helpful is doing an analysis, figuring out why it's broken,
and posting that to the issue. It will make fixing it that much faster.
Also very important is figuring out if it's a problem with their test suite,
or if it's a problem with the module itself. If the module is broken,
Test::Builder 1.5 can declare that version in conflict and prevent upgrading
Test::Builder from breaking existing CPAN installations.
Of course, complete fixes are appreciated.
--
I have a date with some giant cartoon robots and booze.
I have a date with some giant cartoon robots and booze.