On Tue, Jun 11, 2013 at 05:54:52PM +0000, [email protected] wrote:
> The Buildbot has detected a failed build on builder mod_perl_2_trunk while
> building ASF Buildbot.
> Full details are available at:
> http://ci.apache.org/builders/mod_perl_2_trunk/builds/101
> Build Source Stamp: [branch perl/modperl/trunk] 1491887
> Blamelist: gozer
>
> BUILD FAILED: failed compile_2
I'm seeing the same issue on Debian wheezy/amd64:
Test Summary Report
-------------------
t/modules/cgi.t (Wstat: 0 Tests: 5 Failed: 1)
Failed test: 3
t/modules/cgi2.t (Wstat: 0 Tests: 5 Failed: 2)
Failed tests: 1, 4
t/modules/cgipost.t (Wstat: 0 Tests: 6 Failed: 1)
Failed test: 5
t/modules/cgipost2.t (Wstat: 0 Tests: 6 Failed: 1)
Failed test: 5
t/modules/cgiupload.t (Wstat: 0 Tests: 2 Failed: 1)
Failed test: 2
r1491887 enabled t/modperl/local_env.t, but while that one does pass, it
seems to affect other tests. It happens with just
make run_tests TEST_FILES='t/modperl/local_env.t t/modules/cgi.t'
The handler in t/response/TestModules/cgi.pm apparently gets run with
an almost empty environment. Dumping %ENV gives
$VAR1 = {
'LC_CTYPE' => 'fi_FI.UTF-8',
'TestDirective__env_srv1' => 'env_srv1',
'TestDirective__env_srv2' => 'env_srv2',
'APACHE_TEST_HOSTNAME' => 'test.host.name',
'EnvChangeMixedTest' => 'post_config_require',
'PATH' =>
'/home/niko/bin:/usr/local/bin:/usr/bin:/bin:/sbin:/usr/sbin'
};
which is missing MOD_PERL altogether, so the handler throws an exception.
[Tue Jun 18 16:56:29 2013] [error] [client 127.0.0.1] $ENV{MOD_PERL} is not set
at /home/niko/tmp/libapache2-mod-perl2/t/response/TestModules/cgi.pm line 16.\n
So local %ENV still seems to be broken?
--
Niko Tyni [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
