Has anyone else run the tests on win32 with a standard Apache2 service
started and checked the effects? (Does it stop the service? Do some
tests fail? etc)
David Fraser wrote:
Well it certainly causes problems for me :-)
OK It's only one that fails, I didn't read the message clearly. It's
te
Well it certainly causes problems for me :-)
OK It's only one that fails, I didn't read the message clearly. It's
testLoadModule, the first test.
But the existing Apache service is definitely stopped.
What seems to happen is on the first test, it tries to start the
service, then fails, then tri
Hi Nicolas
Of course, one way of fixing this up is ensuring we use a test framework
that cleans everything up.
As it stands, we could potentially have Apache processes left hanging
around...
In fact we could have a service left running that seems to be the
standard Apache service but is in fac
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 gene
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 correcte
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. Do
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 A
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
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, sh
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 document
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 r
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 Subvers
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:
Being the
13 matches
Mail list logo
