Selon Michael G Schwern [EMAIL PROTECTED]:
On Sun, Mar 06, 2005 at 09:54:44PM +0100, S?bastien Aperghis-Tramoni wrote:
Instead of running the code on one server, where it's a problem, why
not running on machines where all prereq modules are already installed,
i.e. on machines where one
Michael G Schwern wrote:
I think it would be a powerful addition to CPAN. If you go to the
distribution page for any module - say, for example, Class::DBI
(http://search.cpan.org/~tmtm/Class-DBI/)
Trouble right there. Now search.cpan.org has to run untrusted code so
a jail would have to be
On Sun, Mar 06, 2005 at 09:54:44PM +0100, S?bastien Aperghis-Tramoni wrote:
Instead of running the code on one server, where it's a problem, why
not running on machines where all prereq modules are already installed,
i.e. on machines where one *wants* to install the module ? Let's add an
On Fri, Mar 04, 2005 at 04:44:42PM -0800, Ofer Nave wrote:
Michael G Schwern wrote:
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank
you). His patch fixed a bug where all tests printed error diags even if
they passed. Additional tests were added to ensure that no output is
sent from diag in successful tests.
While
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank
you). His patch fixed a bug where all tests printed error diags even
if they passed. Additional tests were added to ensure that no output
is sent from diag
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
It still chokes on certain not uncommon constructs like threads.
Michael G Schwern wrote:
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
It still chokes on certain not uncommon
On Fri, Mar 04, 2005 at 04:44:42PM -0800, Ofer Nave wrote:
Is it possible to tell quasi-reliably if the code in question uses
threads and skip it? On that note, is forking also problematic?
Not really. Anywhere within the test or any code called by the test might
use threads. Devel::Cover
Ofer Nave wrote:
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
Renaming thread since only the OP referred to Test::Output.
It occurs to me that the Test::* and ExtUtils::* modules should be the
first stop for the Phalanx project. :)
At least as originally proposed by project
At least as originally proposed by project leader Andy Lester, Phalanx
was supposed to focus on *non-core*,
Not exactly. I just figured it's easier for teams to submit tests back
to individual authors than back to Perl itself. Also, those patches
are more likely to get out into the
11 matches
Mail list logo
