Something weird happens if one tries to clean and test at the same time
with a command like:
make clean test -j2
See https://lists.gnu.org/archive/html/help-make/2021-01/msg00000.html
To be safe until further investigation, we breakup the makefile into 2
files and serialize the first where M2-Planet is built.
For any test there's a directory with a script for each architecture.
These scripts generate intermediate files in the dir during compilation,
with the same names no matter the arch. So if one tries to execute the
scripts in parallel they all fight for the files.
To allow for parallel testing, now we create a temporal dir named after
the arch to isolate the intermediate files. Scripts are patched
accordingly.
This also allows easier clean-up: now, removing the temporal dirs is
almost all that we need (and the per-test .gitignore files are replaced
with a couple of lines in test/.gitignore). A common script replaces
the per-test cleanup.sh. It gets the number of the test as an argument
and takes care of some minor special cases. The makefile is adapted to
use this new test/cleanup_test.sh script.
Those special files are created during the last stage of each test, but
only if the host arch matches the test. They're _not_ isolated here
because it's harder (due to how we do the checksum) and they cannot
collide unless emulation is used and several calls to make are made at
the same time.
- needed to determine start and end of macro directives
- the main parser doesn't need them, so strip out the newline tokens
before parsing to avoid changing it
Jeremiah Orians
Andrius Štikonas
deesix
Sanne Wouda
fosslinux
Jan Nieuwenhuizen