> Those are fragments of my original works. The script should always
kill
> the test servers after completion, and since it can't start the tests
> servers if they're already running I was forced to add checks for
> already-running ones at startup. Old servers are typcially left
running
> because I abort the test scripts with control-c or similar.

> Actually, the script should be fixed to instead at startup detect if
> there's an existing test-server running and if so kill that, then
start
> the new one.

> The reason for this, is that since the test suite is often used in
> test/debug circumstances, it frequently happens that you re-run tests
> and changing the server code between invokes. I've done that mistake
many
> times already, patching e.g httpserver.pl and when I rerun
'runtests.pl'
> the new changes haven't taken effect because there was an old server
> running...

I actually ran into a similar problem (not seeing my httpserver.pl
changes take effect) while running the tests. I assumed by your code
that you had meant to somehow allow the httpserver.pl to stay running
between tests. But in retrospect I can't think of any good reason why
that behavior should be encouraged. So I can agree with trying to kill
an already running httpserver at startup, as you suggested above.

By the way - I apologize for having sent HTML formatted mail. My
"all-knowing" mail administrators have set our default format to
"Outlook Rich text", which apparently gets changed to HTML as it leaves
the company. And I can't change this default (they've locked down the
option to change it). I will endeavor to change the format of curl mails
to plain text before sending, but please forgive me if I forget ;-)

--Kevin
Received on 2001-10-11