| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
... so that linting information gets propagated properly.
|
|
This test verifies properties of just, hence the precise nature of the
just-mr tool does not matter.
|
|
... ensuring we do not regress on the recently fixed race that allowed
file descriptors to reconstructed executables to be kept alive.
|
|
...which do not stage also the debug source and header files (while
in debug mode), as this is unnecessary bloat in the tests.
As the tool-under-test and mr-tool-under-test targets should be
used instead of the regular install targets also in the various
extra rules in end-to-end and utils, move their definition in the
outmost test TARGETS file.
|
|
... and nothing reconstructed for simple (i.e., non-export) targets.
|
|
Add a test that verifies that garbage collection does not violate
the invariants required by the extensional project implicit in
target-level caching.
|
|
This allows better separation and, in particular, repositories
needed only for tests do not have to be provided for building the
tools. This also better documents which dependencies are only needed
for testing.
|
|
|
|
Run build and garbage collection end to end and verify two basic
properties.
- A target used after the the last gc is still available after
another gc, and so are all its parts, even if the output is a
single tree.
- A target not used between to gc is purged from disk and disk
space is not used any more.
|
