On Tue, Dec 04, 2018 at 05:34:56PM +0100, SZEDER Gábor wrote:
> Several test scripts run daemons like 'git-daemon' or Apache, and
> communicate with them through TCP sockets. To have unique ports where
> these daemons are accessible, the ports are usually the number of the
> corresponding test scripts, unless the user overrides them via
> environment variables, and thus all those tests and test libs contain
> more or less the same bit of one-liner boilerplate code to find out
> the port. The last patch in this series will make this a bit more
> complicated.
>
> Factor out finding the port for a daemon into the common helper
> function 'test_set_port' to avoid repeating ourselves.
OK. Looks like this should keep the same port numbers for all of the
existing tests, which I think is good. As nice as choosing random high
port numbers might be for some cases, it can also be confusing when
there are random conflicts.
I've also run into non-random conflicts, but at least once you figure
them out they're predictable (the most confusing I've seen is that adb,
the android debugger, sometimes but not always leaves a daemon hanging
around on port 5561).
> Take special care of test scripts with "low" numbers:
>
> - Test numbers below 1024 would result in a port that's only usable
> as root, so set their port to '10000 + test-nr' to make sure it
> doesn't interfere with other tests in the test suite. This makes
> the hardcoded port number in 't0410-partial-clone.sh' unnecessary,
> remove it.
This part is what made me think a bit more about conflicting with
dynamically allocated ports. Arguably the http parts of t0410 ought to
be in a much higher-numbered script, but I don't know that we've held
over the years very well to the idea that scripts should only depend on
the bits from lower numbered scripts.
> ---
> t/lib-git-daemon.sh | 2 +-
> t/lib-git-p4.sh | 9 +--------
> t/lib-git-svn.sh | 2 +-
> t/lib-httpd.sh | 2 +-
> t/t0410-partial-clone.sh | 1 -
> t/t5512-ls-remote.sh | 2 +-
> t/test-lib-functions.sh | 36 ++++++++++++++++++++++++++++++++++++
> 7 files changed, 41 insertions(+), 13 deletions(-)
The patch itself looks good to me.
> + eval port=\"\${$var}\"
> + case "$port" in
The quotes in the eval'd variable assignment aren't necessary. Usually I
don't mind them in a simple:
FOO="$bar"
even though they're redundant (and there were a few instances in the
prior patch, I think). But here the escaping makes it harder to read,
compared to:
eval port=\$$var
It might be worth simplifying, but I don't feel strongly about it (we'd
run into problems if $var contained spaces with either variant, but I
don't think that's worth caring about).
-Peff
