Do not abuse the "cleandir" target to delete part of the test output.
According to /usr/share/mk/bsd.README, that target is only intended
to delete tags files, and there are no tags files here. Instead,
make sure the "clean" target does not leave any test output behind.

Issue reported and patch OK'ed by bluhm@.

Let the mandoc.db(5) test suite work with parallel make (make -j),
by making sure that different tests use different directory names
for their work such that they do not collide.
As a side benefit, this allows keeping the complete working directories
of the tests until "make cleandir" is run, which may occasionally
help debugging when something breaks.

The failure with make -j was detected and reported by anton@,
who also reviewed, tested, and OK'ed this somewhat lengthy patch.

Make the mandoc.db(5) tests work with BSDOBJDIR set,
by stripping initial parts of paths the do not matter
for the features being tested from man(1) output.

Problem found and reported by, solution developed together with, and
OK anton@

bluhm@ has been pointing out for a long time that the mandoc test suite
was quite nasty in hiding most of the commands being run with '@',
hindering debugging in case anything failed. In particular, it hindered
debugging that had to start from the log of a bulk regress run.

So, finally, resolve this issue by removing almost all these '@'s.
This commit does not change any of the test commands.

If you want to be sure that you don't miss failures, run something like:
make regress 2>&1 | tee make.log ; grep -B1 FAILED make.log

Catch up with mansearch.c rev. 1.60: When finding a bogus database
entry, print a meaningful warning and skip the entry.

The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.

*Add* a test checking that no empty databases get created,
by *removing* one line from the Makefile. Neat, isn't it?

Stop testing the creation and the properties of empty databases.
They are about to be deprecated.
For the tests built on top of them,
use a database containing a single page instead.

Add dependencies to build the required test tools for mandoc on
demand. This is necessary to run make regress without make all or
make build.

Test handling of invalid pointers in the pages table.
In such cases, do not access NULL pointers in dbm_dump.
Make the setup in the run/Makefile a bit more systematic.
Output starts getting too long, so make everything silent;
you can always use "make -dl" to debug specific tests.

adjust database file name and version number to what was committed

test suite for the new mandoc.db(5) format;
will be enabled after committing in src/usr.bin/mandoc

Let the mandoc.db(5) test suite work with parallel make (make -j),
by making sure that different tests use different directory names
for their work such that they do not collide.
As a side benefit, this allows keeping the complete working directories
of the tests until "make cleandir" is run, which may occasionally
help debugging when something breaks.

The failure with make -j was detected and reported by anton@,
who also reviewed, tested, and OK'ed this somewhat lengthy patch.

Make the mandoc.db(5) tests work with BSDOBJDIR set,
by stripping initial parts of paths the do not matter
for the features being tested from man(1) output.

Problem found and reported by, solution developed together with, and
OK anton@

bluhm@ has been pointing out for a long time that the mandoc test suite
was quite nasty in hiding most of the commands being run with '@',
hindering debugging in case anything failed. In particular, it hindered
debugging that had to start from the log of a bulk regress run.

So, finally, resolve this issue by removing almost all these '@'s.
This commit does not change any of the test commands.

If you want to be sure that you don't miss failures, run something like:
make regress 2>&1 | tee make.log ; grep -B1 FAILED make.log

Catch up with mansearch.c rev. 1.60: When finding a bogus database
entry, print a meaningful warning and skip the entry.

The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.

*Add* a test checking that no empty databases get created,
by *removing* one line from the Makefile. Neat, isn't it?

Stop testing the creation and the properties of empty databases.
They are about to be deprecated.
For the tests built on top of them,
use a database containing a single page instead.

Add dependencies to build the required test tools for mandoc on
demand. This is necessary to run make regress without make all or
make build.

Test handling of invalid pointers in the pages table.
In such cases, do not access NULL pointers in dbm_dump.
Make the setup in the run/Makefile a bit more systematic.
Output starts getting too long, so make everything silent;
you can always use "make -dl" to debug specific tests.

adjust database file name and version number to what was committed

test suite for the new mandoc.db(5) format;
will be enabled after committing in src/usr.bin/mandoc

Let the mandoc.db(5) test suite work with parallel make (make -j),
by making sure that different tests use different directory names
for their work such that they do not collide.
As a side benefit, this allows keeping the complete working directories
of the tests until "make cleandir" is run, which may occasionally
help debugging when something breaks.

The failure with make -j was detected and reported by anton@,
who also reviewed, tested, and OK'ed this somewhat lengthy patch.

Make the mandoc.db(5) tests work with BSDOBJDIR set,
by stripping initial parts of paths the do not matter
for the features being tested from man(1) output.

Problem found and reported by, solution developed together with, and
OK anton@

bluhm@ has been pointing out for a long time that the mandoc test suite
was quite nasty in hiding most of the commands being run with '@',
hindering debugging in case anything failed. In particular, it hindered
debugging that had to start from the log of a bulk regress run.

So, finally, resolve this issue by removing almost all these '@'s.
This commit does not change any of the test commands.

If you want to be sure that you don't miss failures, run something like:
make regress 2>&1 | tee make.log ; grep -B1 FAILED make.log

Catch up with mansearch.c rev. 1.60: When finding a bogus database
entry, print a meaningful warning and skip the entry.

The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.

*Add* a test checking that no empty databases get created,
by *removing* one line from the Makefile. Neat, isn't it?

Stop testing the creation and the properties of empty databases.
They are about to be deprecated.
For the tests built on top of them,
use a database containing a single page instead.

Add dependencies to build the required test tools for mandoc on
demand. This is necessary to run make regress without make all or
make build.

Test handling of invalid pointers in the pages table.
In such cases, do not access NULL pointers in dbm_dump.
Make the setup in the run/Makefile a bit more systematic.
Output starts getting too long, so make everything silent;
you can always use "make -dl" to debug specific tests.

adjust database file name and version number to what was committed

test suite for the new mandoc.db(5) format;
will be enabled after committing in src/usr.bin/mandoc

bluhm@ has been pointing out for a long time that the mandoc test suite
was quite nasty in hiding most of the commands being run with '@',
hindering debugging in case anything failed. In particular, it hindered
debugging that had to start from the log of a bulk regress run.

So, finally, resolve this issue by removing almost all these '@'s.
This commit does not change any of the test commands.

If you want to be sure that you don't miss failures, run something like:
make regress 2>&1 | tee make.log ; grep -B1 FAILED make.log

Catch up with mansearch.c rev. 1.60: When finding a bogus database
entry, print a meaningful warning and skip the entry.

The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.

*Add* a test checking that no empty databases get created,
by *removing* one line from the Makefile. Neat, isn't it?

Stop testing the creation and the properties of empty databases.
They are about to be deprecated.
For the tests built on top of them,
use a database containing a single page instead.

Add dependencies to build the required test tools for mandoc on
demand. This is necessary to run make regress without make all or
make build.

Test handling of invalid pointers in the pages table.
In such cases, do not access NULL pointers in dbm_dump.
Make the setup in the run/Makefile a bit more systematic.
Output starts getting too long, so make everything silent;
you can always use "make -dl" to debug specific tests.

adjust database file name and version number to what was committed

test suite for the new mandoc.db(5) format;
will be enabled after committing in src/usr.bin/mandoc

Catch up with mansearch.c rev. 1.60: When finding a bogus database
entry, print a meaningful warning and skip the entry.

The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.

*Add* a test checking that no empty databases get created,
by *removing* one line from the Makefile. Neat, isn't it?

Stop testing the creation and the properties of empty databases.
They are about to be deprecated.
For the tests built on top of them,
use a database containing a single page instead.

Add dependencies to build the required test tools for mandoc on
demand. This is necessary to run make regress without make all or
make build.

Test handling of invalid pointers in the pages table.
In such cases, do not access NULL pointers in dbm_dump.
Make the setup in the run/Makefile a bit more systematic.
Output starts getting too long, so make everything silent;
you can always use "make -dl" to debug specific tests.

adjust database file name and version number to what was committed

test suite for the new mandoc.db(5) format;
will be enabled after committing in src/usr.bin/mandoc