There's an old thread below about testing on Win32.

As afar as I can recall, Nicolas Lehuen is the only guy who's been able
to run the tests on win32
Has anybody else been able to? Can we put together some hints as to how
to do it?

David

David Fraser wrote:

> Nicolas Lehuen wrote:
> 
> Brilliant :-)
> 
> Great, thanks
> 
> Surely we could write code to figure these out? We work out many of
> them in setup.py.in / win32_postinstall.py anyway...
> 
> OK - it seems the test framework leads at least a bit of documentation
> as to how to run on Windows
> 
> Nothing like bothering people :-)
> So do these tests run for you?
> The disturbing thing for me was that the seem to fail without any
> error messages being produced by apache, even in the test/logs/* files
> It turns out that if the service can't write to the error log file, it
> fails and logs a message in the Windows Event log, rather than to the
> console.
> This is odd because it actually opens the log files itself.
> I suspect this is because it actually runs using a different user as a
> service...
>
> Anyway I should have been testing the earlier betas so I'm doing
> catchup :-)
> Cheers
> David
>

[ Post a follow-up to this message ]

Hi David,

To follow my old promise, I've just checked in a bit of documentation on how
to run the test suite, including on Win32. I've also added a few self-test
in the test module, so that the most obvious setup mistakes are notified to
the user.

Here is the documentation, directly from the Subversion repository :

http://svn.apache.org/repos/asf/htt...unk/test/README

This should eventually be converted to TeX and integrated into the real
documentation, but for various reasons this way is the quickest way to put
it online. It's much better than the previous README file anyway (it was
basically saying "keep out unless you know what you're doing" ;).

Hope this helps.

Regards,
Nicolas



2005/12/5, David Fraser <davidf@sjsoft.com>:
>
> There's an old thread below about testing on Win32.
>
> As afar as I can recall, Nicolas Lehuen is the only guy who's been able
> to run the tests on win32
> Has anybody else been able to? Can we put together some hints as to how
> to do it?
>
> David
>

[ Post a follow-up to this message ]

I'm a bit confused by:

- The only trick is that you'll have to stop your Apache server
before launching
the test, as the start/stop command can only apply to one single
Apache instance.

Does this apply to UNIX as well as Win32?

I ask as I have never bothered to explicitly shut down any running
instance of
Apache, yet haven't noticed any problems with running the tests. If
this is a Win32
specific instruction, you might want to note it as such. On UNIX
systems, where
the web server may be doing real work, people may not want to shut it
down just
to be able to test a new separate version of mod_python that hasn't
been installed
yet.

Graham

On 06/12/2005, at 8:02 AM, Nicolas Lehuen wrote:
[vbcol=seagreen]
> Hi David,
>
> To follow my old promise, I've just checked in a bit of documentation
> on how to run the test suite, including on Win32. I've also added a
> few self-test in the test module, so that the most obvious setup
> mistakes are notified to the user.
>
> Here is the documentation, directly from the Subversion repository :
>
> http://svn.apache.org/repos/asf/htt...unk/test/README
>
> This should eventually be converted to TeX and integrated into the
> real documentation, but for various reasons this way is the quickest
> way to put it online. It's much better than the previous README file
> anyway (it was basically saying "keep out unless you know what you're
> doing" ;).
>
> Hope this helps.
>
> Regards,
> Nicolas
>
>
>
> 2005/12/5, David Fraser <davidf@sjsoft.com>: 

[ Post a follow-up to this message ]

Nicolas Lehuen wrote:

> Hi David,
>
> To follow my old promise, I've just checked in a bit of documentation
> on how to run the test suite, including on Win32. I've also added a
> few self-test in the test module, so that the most obvious setup
> mistakes are notified to the user.
>
> Here is the documentation, directly from the Subversion repository :
>
> http://svn.apache.org/repos/asf/htt...unk/test/README
> <http://svn.apache.org/repos/asf/htt...unk/test/README>
>
> This should eventually be converted to TeX and integrated into the
> real documentation, but for various reasons this way is the quickest
> way to put it online. It's much better than the previous README file
> anyway (it was basically saying "keep out unless you know what you're
> doing" ;).
>
> Hope this helps.

Thanks Nicolas, that was quick :-)

OK Now I know I'm following the correct procedure ...

At first all the tests failed... then I realised this was because I was
running it off a shared drive that the service didn't have access to as
it runs under a different account, so it simply fails to start with no
error messages... (Hmmm, sure I've done this before...)

After switching to a local drive, all tests pass! Hurray! This was on my
own built version, so the build process works nicely too...

So +1 for me on the already-released 3.2.5b on win32, and I should be
able to run tests in the future

Cheers
David

[ Post a follow-up to this message ]

My bad... It seems it's not necessary to stop the Apache server. I was a bit
confused by the Apache Monitor, a Win32 application putting an icon in the
tray area showing the state of the Apache server and allowing you to control
it. Turns out the monitor is a bit messed up by the test procedure, showing
the status of the test server and not the "official" server. Thus when the
tests stop, the monitor shows that the Apache server is stopped even though
the "official" one isn't.

I have changed the documentation accordingly.

Regards,
Nicolas

2005/12/5, Graham Dumpleton <grahamd@dscpl.com.au>:
>
> I'm a bit confused by:
>
>    - The only trick is that you'll have to stop your Apache server
> before launching
>    the test, as the start/stop command can only apply to one single
> Apache instance.
>
> Does this apply to UNIX as well as Win32?
>
> I ask as I have never bothered to explicitly shut down any running
> instance of
> Apache, yet haven't noticed any problems with running the tests. If
> this is a Win32
> specific instruction, you might want to note it as such. On UNIX
> systems, where
> the web server may be doing real work, people may not want to shut it
> down just
> to be able to test a new separate version of mod_python that hasn't
> been installed
> yet.
>
> Graham
>
> On 06/12/2005, at 8:02 AM, Nicolas Lehuen wrote:
> 
>
>

[ Post a follow-up to this message ]

I'm sure this is Win32 only.

We could even remove the requirement on Win32 by using an alternative
service name that we create and destroy as required.
I've opened a Jira issue with a patch for this:
http://issues.apache.org/jira/browse/MODPYTHON-95

Graham Dumpleton wrote:

> I'm a bit confused by:
>
>   - The only trick is that you'll have to stop your Apache server
> before launching
>   the test, as the start/stop command can only apply to one single
> Apache instance.
>
> Does this apply to UNIX as well as Win32?
>
> I ask as I have never bothered to explicitly shut down any running
> instance of
> Apache, yet haven't noticed any problems with running the tests. If
> this is a Win32
> specific instruction, you might want to note it as such. On UNIX
> systems, where
> the web server may be doing real work, people may not want to shut it
> down just
> to be able to test a new separate version of mod_python that hasn't
> been installed
> yet.
>
> Graham
>
> On 06/12/2005, at 8:02 AM, Nicolas Lehuen wrote:
> 
>

[ Post a follow-up to this message ]

Woops, I've marked the issue as resolved since I've corrected the
documentation, but I've not taken your patch into account. I'm not really
sure it's required, though, since the only problem is that the Apache
Monitor gets a bit  confused by the test server, buit everything else works
correctly. Does your patch fixes the problem with the Apache Monitor ?

Regards,
Nicolas

2005/12/6, David Fraser <davidf@sjsoft.com>:
>
> I'm sure this is Win32 only.
>
> We could even remove the requirement on Win32 by using an alternative
> service name that we create and destroy as required.
> I've opened a Jira issue with a patch for this:
> http://issues.apache.org/jira/browse/MODPYTHON-95
>
> Graham Dumpleton wrote:
> 
> able 
> how 
>
>

[ Post a follow-up to this message ]

In parallel, I opened http://issues.apache.org/jira/browse/MODPYTHON-95
which changes the service name, and prevents this confusion anyway...
The patch could be improved, perhaps we should make this automatic on
win32...

Nicolas Lehuen wrote:

> My bad... It seems it's not necessary to stop the Apache server. I was
> a bit confused by the Apache Monitor, a Win32 application putting an
> icon in the tray area showing the state of the Apache server and
> allowing you to control it. Turns out the monitor is a bit messed up
> by the test procedure, showing the status of the test server and not
> the "official" server. Thus when the tests stop, the monitor shows
> that the Apache server is stopped even though the "official" one isn't.
>
> I have changed the documentation accordingly.
>
> Regards,
> Nicolas
>
> 2005/12/5, Graham Dumpleton <grahamd@dscpl.com.au
> <mailto:grahamd@dscpl.com.au>>:
>
>     I'm a bit confused by:
>
>        - The only trick is that you'll have to stop your Apache server
>     before launching
>        the test, as the start/stop command can only apply to one single
>     Apache instance.
>
>     Does this apply to UNIX as well as Win32?
>
>     I ask as I have never bothered to explicitly shut down any running
>     instance of
>     Apache, yet haven't noticed any problems with running the tests. If
>     this is a Win32
>     specific instruction, you might want to note it as such. On UNIX
>     systems, where
>     the web server may be doing real work, people may not want to shut it
>     down just
>     to be able to test a new separate version of mod_python that hasn't
>     been installed
>     yet.
>
>     Graham
>
>     On 06/12/2005, at 8:02 AM, Nicolas Lehuen wrote:
> 
>     documentation 
>     repository : 
>     you're 
>     <mailto:davidf@sjsoft.com>>: 
>     as to 
>
>

[ Post a follow-up to this message ]

Hi Nicolas

Interesting, I never even tried running it the same time as the service,
so I can see that actually works now (except for the monitor problem).
Yes, my patch fixes the problem with the monitor

David

Nicolas Lehuen wrote:

> Woops, I've marked the issue as resolved since I've corrected the
> documentation, but I've not taken your patch into account. I'm not
> really sure it's required, though, since the only problem is that the
> Apache Monitor gets a bit  confused by the test server, buit
> everything else works correctly. Does your patch fixes the problem
> with the Apache Monitor ?
>
> Regards,
> Nicolas
>
> 2005/12/6, David Fraser <davidf@sjsoft.com <mailto:davidf@sjsoft.com>>:
>
>     I'm sure this is Win32 only.
>
>     We could even remove the requirement on Win32 by using an alternative
>     service name that we create and destroy as required.
>     I've opened a Jira issue with a patch for this:
>     http://issues.apache.org/jira/browse/MODPYTHON-95
>
>     Graham Dumpleton wrote:
> 
>     shut it 
>     documentation 
>     repository : 
>     quickest 
>     file 
>     you're 
>     <mailto:davidf@sjsoft.com>>: 
>     been able 
>     as to how 
>
>

[ Post a follow-up to this message ]

David,

Though your code seems perfect, I'm a bit worried about installing a
service, even temporary, for testing purposes.

It adds another point where the test could fail for setup reasons, and
should the test end unexpectedly, the tester's system has an extra service
which points to a temporary generated configuration file.

Since everything seems OK without the service layer, I'd rather we keep the
test suite as is and not introduce some extra feature that we'll have to
debug later on. Nothings kills me more than debugging the tests .

Regards,
Nicolas

2005/12/6, David Fraser <davidf@sjsoft.com>:
>
> Hi Nicolas
>
> Interesting, I never even tried running it the same time as the service,
> so I can see that actually works now (except for the monitor problem).
> Yes, my patch fixes the problem with the monitor
>
> David
>
> Nicolas Lehuen wrote:
> 
> alternative 
> If 
> hasn't 
> a 
> http://svn.apache.org/repos/asf/htt...unk/test/README 
> the 
>
>

[ Post a follow-up to this message ]