mod_env test

[john sachs <js...@covalent.net>]

so here's the deal.
i wrote a test for mod_env and 2 tests are failing.  these look to me to be valid tests, but i dont know how mod_env is supposed to work in this instance.

what i'm doing in the two tests are setting an environment variable and then using UnsetEnv to unset it and attempting to verify that it is indeed unset.  from the doc, you'd think this would work, but in both cases, it is still set.

so do i check in a test that is failing or wait?
-j

Re: mod_env test

[john sachs <js...@covalent.net>]

so there is already a bug for this.  #7528.
UnsetEnv does not work in the main body of httpd.conf.

On Mon, Aug 20, 2001 at 10:49:57AM -0700, john sachs wrote:
+ so here's the deal.
+ i wrote a test for mod_env and 2 tests are failing.  these look to me to be valid tests, but i dont know how mod_env is supposed to work in this instance.
+ 
+ what i'm doing in the two tests are setting an environment variable and then using UnsetEnv to unset it and attempting to verify that it is indeed unset.  from the doc, you'd think this would work, but in both cases, it is still set.
+ 
+ so do i check in a test that is failing or wait?
+ -j

Re: mod_env test

[Doug MacEachern <do...@covalent.net>]

On Mon, 20 Aug 2001, john sachs wrote:

> i wrote a test for mod_env and 2 tests are failing.

they work now.
 
> so do i check in a test that is failing or wait?

yeah, failing tests is good motivation to fix bugs :)