CPAN Testers

  • Website:
  • About: This is the new account for incidental and summary updates to what's happening with the CPAN Testers. For all the latest news and views please see our blog.
Subscribe to feed Recent Actions from CPAN Testers

  • Ingy döt Net commented on CPAN Day - 317 Uploads and 21 Guns

    Like I said, this was all just good fun to celebrate CPAN Day.

  • Peter Rabbitson commented on CPAN Testers & pre-requisite reporting

    I think a much more robust solution would be to introduce an extra "supertype" to the results. Currently we have PASS FAIL NA UNKNOWN, which can be relatively painlessly extended to REGULAR.PASS REGULAR.FAIL ... DEVREL.PASS DEVREL.FAIL...

    The "DEVREL" prefix will be appended as soon as there is *anything* in the chain that is, well - a devrel as understood by PAUSE. Then filtering these results in the consumers will be beyond trivial, while the metabase infrastructure itself won't need much tweaking at all.

  • Ether commented on CPAN Testers & pre-requisite reporting

    > The "DEVREL" prefix will be appended as soon as there is *anything* in the chain

    I like this a lot, and it's similar to what I was thinking too. However, I realize now there's a problem here -- the release status of a module can't always be determined from the module itself (at least, not the $VERSION) - you need the distribution metadata to determine that.

    There is one (relatively) simple way to handle misdirected failures, however -- allow a mechanism to redirect them. We've already got nearly that, with the new admin site -- just modify the interface to allow redirectin…

  • exodist7 commented on CPAN Testers & pre-requisite reporting

    I agree with Peter Rabbitsons solution, I left a comment to that same effect in the original post.

    I am the one making these Test::More changes, and I would have been a lot more reluctant to make these alpha releases if I know it would give other people red marks. I myself judge modules based on red vs green counts.

  • Peter Rabbitson commented on CPAN Testers & pre-requisite reporting

    I still maintain that "oh, changing the set of test tags beyond the current 4 is too hard" is a dead-end strategy. In order to remain relevant the cpantesters infrastructure must allow for extra test-type additions anyway - the current set is too limited.

    In addition I do not believe (given I know and admire the skill of everyone involved) that the current stack is written so badly, that it will be a monumental effort to allow for "super-namespacing" of the test results. At worst it should be a couple day slog, perfect for a hackathon... if there only was an upcoming one ;)


Subscribe to feed Responses to Comments from CPAN Testers

About is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.