Title | Perl warnings generated when test suite runs Bugzilla scripts |
Status | suspended |
Priority | optional |
Assigned user | Nick Barnes |
Organization | Ravenbrook |
Description | Running the P4DTI test suite on some machines generates a Perl warning message, every time a Bugzilla script is invoked. The Cwd Perl module in some versions of Perl likes $ENV{PATH} to be set to something, and this conflicts with the code in Bugzilla which detaint the environment. The warning message is as follows: Use of uninitialized value in split at /usr/local/lib/perl5/5.6.1/Cwd.pm line 103 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl tells you what operation you used the undefined value in. Note, however, that perl optimizes your program and the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. |
Analysis | A possible workaround might be to set $ENV{PATH} to the empty string instead of unsetting it. |
How found | automated_test |
Evidence | Run the automated test suite on thrush with Bugzilla 2.14.5 and perl-5.6.1_13. |
Observed in | 2.0.0 |
Created by | Nick Barnes |
Created on | 2003-11-05 13:32:01 |
Last modified by | Nick Barnes |
Last modified on | 2018-07-05 17:28:10 |
History | 2003-11-05 NB Created. 2018-07-05 NB Suspended because the P4DTI is obsolete. |