.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{ . if \nF \{ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "CPAN::Reporter::FAQ 3pm" .TH CPAN::Reporter::FAQ 3pm "2016-07-20" "perl v5.22.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" CPAN::Reporter::FAQ \- Answers and tips for using CPAN::Reporter .SH "VERSION" .IX Header "VERSION" version 1.2018 .SH "REPORT GRADES" .IX Header "REPORT GRADES" .SS "Why did I receive a report?" .IX Subsection "Why did I receive a report?" Historically, \s-1CPAN\s0 Testers was designed to have each tester send a copy of reports to authors. This philosophy changed in September 2008 and \s-1CPAN\s0 Testers tools were updated to no longer copy authors, but some testers may still be using an older version. .SS "Why was a report sent if a prerequisite is missing?" .IX Subsection "Why was a report sent if a prerequisite is missing?" As of CPAN::Reporter 0.46, \s-1FAIL\s0 and \s-1UNKNOWN\s0 reports with unsatisfied prerequisites are discarded. Earlier versions may have sent these reports out by mistake as either an \s-1NA\s0 or \s-1UNKNOWN\s0 report. .PP \&\s-1PASS\s0 reports are not discarded because it may be useful to know when tests passed despite a missing prerequisite. \s-1NA\s0 reports are sent because information about the lack of support for a platform is relevant regardless of prerequisites. .SH "SENDING REPORTS" .IX Header "SENDING REPORTS" .SS "Why did I get an error sending a test report?" .IX Subsection "Why did I get an error sending a test report?" Historically, test reports were sent via ordinary email. The most common reason for errors sending a report back then was that many Internet Service Providers (\s-1ISP\s0's) would block outbound \s-1SMTP \s0(email) connections as part of their efforts to fight spam. .PP Since 2010, test reports are sent to the \s-1CPAN\s0 Testers Metabase over \s-1HTTPS.\s0 The most common reason for failures are systems which upgraded CPAN::Reporter but are still configured to use the deprecated and unsupported email system instead of Metabase for transport. .PP If you are unsure which transport mechanism you're using, look for the \&\f(CW\*(C`transport\*(C'\fR rule in the \f(CW\*(C`.cpanreporter/config.ini\*(C'\fR file, in the user's home directory. See CPAN::Reporter::Config for details on how to set the \f(CW\*(C`transport\*(C'\fR option for Metabase. .PP Other errors could be caused by the absence of the \&\f(CW\*(C`.cpanreporter/metabase_id.json\*(C'\fR file in the user's home directory. This file should be manually created prior to sending any reports, via the \&\f(CW\*(C`metabase\-profile\*(C'\fR program. Simply run it and fill in the information accordingly, and it will create the \f(CW\*(C`metabase_id.json\*(C'\fR file for you. Move that file to your \f(CW\*(C`.cpanreporter\*(C'\fR directory and you're all set. .PP If you experience intermittent network issues, you can set the \&'retry_submission' option to make a second attempt at sending the report a few seconds later, in case the first one fails. This could be useful for extremely slow connections. .PP Finally, lack of Internet connection or firewall filtering will prevent the report from reaching the \s-1CPAN\s0 Testers servers. If you are experiencing \&\s-1HTTPS\s0 issues or messages complaining about \s-1SSL\s0 modules, try installing the LWP::Protocol::https module and trying again. If all fails, you may still change the transport uri to use \s-1HTTP\s0 instead of \s-1HTTPS,\s0 though this is \fInot\fR recommended. .SS "Why didn't my test report show up on \s-1CPAN\s0 Testers?" .IX Subsection "Why didn't my test report show up on CPAN Testers?" There is a delay between the time reports are sent to the Metabase and when they they appear on the \s-1CPAN\s0 Testers website. There is a further delay before summary statistics appear on search.cpan.org. If your reports do not appear after 24 hours, please contact the cpan-testers-discuss email list () or join the \&\f(CW\*(C`#cpantesters\-discuss\*(C'\fR \s-1IRC\s0 channel on \f(CW\*(C`irc.perl.org\*(C'\fR. .SH "CPAN TESTERS" .IX Header "CPAN TESTERS" .SS "Where can I find out more about \s-1CPAN\s0 Testers?" .IX Subsection "Where can I find out more about CPAN Testers?" A good place to start is the \s-1CPAN\s0 Testers Wiki: .SS "Where can I find statistics about reports sent to \s-1CPAN\s0 Testers?" .IX Subsection "Where can I find statistics about reports sent to CPAN Testers?" \&\s-1CPAN\s0 Testers statistics are compiled at .SS "How do I make sure I get credit for my test reports?" .IX Subsection "How do I make sure I get credit for my test reports?" To get credit in the statistics, use the same Metabase profile file and the same email address wherever you run tests. .SH "SEE ALSO" .IX Header "SEE ALSO" .IP "\(bu" 4 CPAN::Testers .IP "\(bu" 4 CPAN::Reporter .IP "\(bu" 4 Test::Reporter .SH "AUTHOR" .IX Header "AUTHOR" David Golden .SH "COPYRIGHT AND LICENSE" .IX Header "COPYRIGHT AND LICENSE" This software is Copyright (c) 2006 by David Golden. .PP This is free software, licensed under: .PP .Vb 1 \& The Apache License, Version 2.0, January 2004 .Ve