On Fri, 21 Dec 2007 13:34:49 -0600 (CST), Dave Rolsky [EMAIL PROTECTED]
said:
However, usually I end up needing to investigate aspects of the
testers platform, often by having them run snippets of Perl code from
the shell, or asking them to try a patch. There's not much you can do
On Sat, 22 Dec 2007 14:22:05 +0100, [EMAIL PROTECTED] (Andreas J. Koenig)
said:
1. You get a fail report with an error message that doesn't tell you
exactly what went wrong.
2. You rewrite your test in a way that it does tell you more.
3. Release.
4. If you now understand
On Saturday 22 December 2007 05:22:05 Andreas J. Koenig wrote:
1. You get a fail report with an error message that doesn't tell you
exactly what went wrong.
2. You rewrite your test in a way that it does tell you more.
3. Release.
4. If you now understand the problem, fix it, else goto
On Saturday 22 December 2007 12:44:12 David Golden wrote:
On Dec 22, 2007 2:12 PM, chromatic [EMAIL PROTECTED] wrote:
I'm not sure how to write a test for Tester's installation of Perl is
fatally broken and can't actually install anything.
Oh, come on. This is Perl, after all.
#
On 22/12/2007, David Golden [EMAIL PROTECTED] wrote:
On Dec 22, 2007 3:52 PM, chromatic [EMAIL PROTECTED] wrote:
Let me rephrase then.
I feel dirty writing tests just to trip up testers who can't set up working
testing environments.
Is this really a problem? Let me flip this around --
On Saturday 22 December 2007 16:48:29 Michael G Schwern wrote:
The I installed to a directory with a space in the path is an example of
CPAN Testers working as expected. It found and highlighted an annoying bug
that the rest of us either ignore or work around.
CPAN Testers reporting failures
chromatic wrote:
On Saturday 22 December 2007 16:48:29 Michael G Schwern wrote:
The I installed to a directory with a space in the path is an example of
CPAN Testers working as expected. It found and highlighted an annoying bug
that the rest of us either ignore or work around.
CPAN Testers
On Dec 22, 2007 8:26 PM, chromatic [EMAIL PROTECTED] wrote:
CPAN Testers reporting failures in every module they test and not stopping to
ask Hey, is it possible that not everything else in the world is broken? is
*not* an example of CPAN Testers working as expected.
Environments where it's
On Saturday 22 December 2007 21:58:46 David Golden wrote:
These are not simple modules. Assuming that some smoker can get these
to successfully send you a report, then which scenario seems more
likely:
(a) that the smoker's installation is fundamentally broken
(b) that your distribution
chromatic wrote:
I just went through a sampling of fail reports for my stuff. There was one
legitimate packaging bug, and a couple of legitimate errors due to updates to
Perl. About 35% of the other reports are these.
I love the Illegal seek error message:
10 matches
Mail list logo
