If @$cmd is causing the problem, you should identify what's going on (see below). You could then try to invoke the
program with the given arguments to dive into the problem (hopefully %ENV was not modified and the files used still exist!).
However, you could add
- note "Now running '@$cmd'..."; and/or
- ok(...) or diag "Getting from (@$cmd): stdout=... stderr=..."; (Diagnostics)
to narrow down the problem. Use i.e. prove -v ... which shows all note(...)'s.
You colud also add more logging to the modules/scripts under test (e.g Log::Log4perl).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
