We need this to test includes and relative paths.

Here we use these directives to replace, extend, or clear values in
torrc.defaults and in torrc.

I'm not planning to use "example" as the name for all of them, but
these first three _are_ simple examples.

This script takes a set of example torrcs and command-lines from
src/test/conf_examples.  If a success is expected, it runs "tor
--dump-config" and compares the result with the one we expect.  If a
failure is expected, it runs "tor --verify-config" and greps for the
error we expect.

Any floating point value too positive or negative to distinguish
from +/-Inf, or too small to distinguish from +/-0, is an
over/underflow.

GCC complains that we are using too many variables here, probably
because of the sheer number of locals used for our tinytest macros.
Eventually we should fix that (see 30968), but this commit just
makes the "note" go away by splitting the test function into two.

Instead, put them in the function itself.

This is an attempt to fix the gcc warning about the "variable
tracking size limit exceeded".

Tests should now pass again.

This commit was automatically generated by running
scripts/maint/rectify_include_paths.py .

This commit only does code movement, and does not clean up after
itself.  As such, it will break compilation.  I'm separating it for
ease of review.

confparse.[ch] will need these; checkIncludes confirms that we have
not introduced a cycle.

Nick Mathewson authored Sep 10, 2019 and David Goulet committed Sep 11, 2019

See also ticket 31654.

Nick Mathewson authored Sep 10, 2019 and David Goulet committed Sep 11, 2019

Here we make it clear we're only looking at listable variable names,
not at whether the variables themselves are gettable.

Also, remove an extraneous h.

(This commit is not a fixup, because of rebase conflicts.)

Nick Mathewson authored Sep 05, 2019 and David Goulet committed Sep 11, 2019

(This option tests our existing behavior, not necessarily the most
sensible behavior.)

Nick Mathewson authored Sep 05, 2019 and David Goulet committed Sep 11, 2019

The old names remain as #defines that cause variables to get one or
more flags.

Now every flag-testing function in confparse.c tests exactly one flag.

Nick Mathewson authored Sep 05, 2019 and David Goulet committed Sep 11, 2019

Since the flags are now stored with compatible numbering, we can
just OR them together and see whether the flag we want is in the
result.

(Net code removal!)