Re: Fwd: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received
Michael G Schwern wrote: As for the social problem, the BSD testers could try to help out with whatever the problem is. FWIW, I do, *if* the author gets in touch with me. It's not practical for me to try to help solve all the problems I find, but if an author cares enough to contact me, then I'm happy to run more tests for him, try out patches, or give him the s3kr1t keys to the guest account on my testing machines. I would hope that most testers would do at least some of this. -- David Cantrell | Official London Perl Mongers Bad Influence Hail Caesar! Those about to vi ^[ you!
Re: Fwd: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received
--- Michael G Schwern [EMAIL PROTECTED] wrote: It is particularly near to my heart as Test::More has a similiar problem with thread tests and I'm not sure what to do about it. I've discovered that handing the problem to Andy Armstrong and batting my eyelashes works wonders. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
Fwd: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received
Someone (MLEHMANN) doesn't like smoking... That was a test report generated by CPAN::Reporter. It hadn't previously occurred to me that test reports might cause offence... Begin forwarded message: From: [EMAIL PROTECTED] Date: 19 December 2007 00:35:18 GMT To: [EMAIL PROTECTED] Subject: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread- multi 6.2-release' has NOT been received Please do not submit automatically generated test reports, I found most of them to be bogus and it is hard to wade through them to find the rare report that is not (e.g. yours :). If you want to test the module you tried to test, please do so seriously and submit any bug report in the normal way (usually by mail). -- Andy Armstrong, Hexten
Re: Fwd: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received
On Tuesday 18 December 2007 17:27:24 Andy Armstrong wrote: Someone (MLEHMANN) doesn't like smoking... That was a test report generated by CPAN::Reporter. It hadn't previously occurred to me that test reports might cause offence... Didn't you get a whole slew of them a while back where the problem was that that the reporter hadn't properly configured Windows to build modules? How about the one where the reporter had configured CPAN never to follow dependencies? -- c
Re: Fwd: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received
chromatic wrote: On Tuesday 18 December 2007 17:27:24 Andy Armstrong wrote: Someone (MLEHMANN) doesn't like smoking... That was a test report generated by CPAN::Reporter. It hadn't previously occurred to me that test reports might cause offence... Didn't you get a whole slew of them a while back where the problem was that that the reporter hadn't properly configured Windows to build modules? How about the one where the reporter had configured CPAN never to follow dependencies? That said, looking through IO::AIO's failures they seem reasonably legit to me. It has trouble on BSD, and some other systems, a useful thing to know. IO::AIO lacks any special INSTALL instructions or special notes about BSD in general. There are a couple notes generated by the Makefile.PL about FreeBSD and threading and Linux and malloc issues, but that will whiz by and likely be completely missed. So even a human installer would not know what to do. Anyhow, what's clear is there is a problem with IO::AIO. It hasn't been addressed properly by the author. While it's frustrating to get a constant stream of your shit is broke, his shit is indeed broke. This is a clear case of CPAN Testers technology working as expected and tickling a social problem. It is particularly near to my heart as Test::More has a similiar problem with thread tests and I'm not sure what to do about it. There was the suggested author does not care marker for tests which might fail but are only for the information of the installer -- the author already knows about them, don't report the failure. As for the social problem, the BSD testers could try to help out with whatever the problem is. On Marc's side he could ask for help instead of asking everyone to turn off the immensely useful automated testing. It could also use an INSTALL doc and have the Makefile.PL warnings be more prominent with perhaps a pause, beep or a well-behaved Do you wish to continue? [No]. -- I am somewhat preoccupied telling the laws of physics to shut up and sit down. -- Vaarsuvius, Order of the Stick http://www.giantitp.com/comics/oots0107.html