David Golden wrote:
On Mon, Sep 29, 2008 at 10:29 AM, Martin J. Evans
<[EMAIL PROTECTED]> wrote:
1. just started happening but whilst testing LaTeX-Table-0.9.3 got an open3
error that suggests to me the command line is too long:
t/pod-coverage.......open3: exec of /home/martin/perl10/bin/perl -w
-I/home/martin/perl10/.cpan/build/LaTeX-Table-0.9.3-86IoAF/blib/lib...
a very long line truncated and ending in "[Output truncated after 50K]".
How do you deal with this?
Can you send a link to the report in questions?
I have not sent it yet as it looked like a failure with my smoking
rather than a failure with the module. It is still sat in vi waiting for
me to edit it.
The 50k cutoff is a CPAN::Reporter thing to try to cut down on the
load on the perl.org mailing list servers. It's on the Todo list to
give the first 25k and last 25k instead of just truncating. That will
cut down on stuff but still show the error at the end.
The full report is now at
ftp://ftp.easysoft.com/pub/LaTeX-Table-0.9.3_report.txt
but this is just a copy of what is sat in my editor right now (I have
edit all failures as default).
2. Modules which prompt for things
e.g. DBD::Pg 2.10.7 prompts for:
Path to pg_config?
How do I answer this - firstly, I think that is supposed to use prompt to
avoid prompting and secondly I don't have a pg_config file.
Programs that don't use the EU::MM "prompt" command don't respect the
environment variable to use defaults. For these, I just disable them
with distroprefs. See the CPAN::Reporter::Smoker docs for details. I
keep my distroprefs under a public git repository:
http://echo.dagolden.com/git/?p=distroprefs;a=summary
You can click on 'tree' to see them. And you're welcome to use git to
clone them for your own use. However, note that I have a pretty
aggressive policy of just disabling any version of any distribution
that ever gave me problems. That may not suit your style. The
distroprefs are generally grouped by type of issue, if I could tell
what it was. If you have questions, email back on a separate thread.
Thanks.
3. PHRED/Apache-Test-1.30.tar.gz continually outputs:
There are other modules that seem to loop if run non-interactively.
Disable with distroprefs.
Will do.
4. Some modules fail to test, hanging:
I usually kill them ctrl-c and then disable with distroprefs.
However, if you're on Unix, you can install Proc::ProcessTable and
Proc::Killfam and use CPAN::Reporter's "command_timeout" advanced
config option to kill such processes after a certain period of time.
You can also do this for Win32 if you have Win32::Job installed, but
there is a small but non-trivial risk that you can wedge your perl
executable requiring a reboot due to the nasty way that Windows does
process termination.
I'm on unix so I'll try this.
5. Loads of modules seem to use LWP but not support $ua->env_proxy so never
spot I'm behind a firewall and hence have http_proxy env var set. Obviously
these all fail in some way.
Can't help you there. Maybe use some sort of transparent proxy in between?
-- David
I can't help feeling these are genuine failures - surely loads of people
are behind proxies these days. It is not exactly difficult to add env_proxy.
Thanks for the feedback.
Martin
