Age | Commit message (Collapse) | Author |
|
... even if remote-execution arguments are given. Also verify
that failure is correctly reflected in the exit code.
|
|
|
|
... so that linting information gets propagated properly.
|
|
|
|
...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.
|
|
...instead of using absolute values.
This was the desidered outcome all along and now it can be done
right thanks to the recently added multiplication expression.
|
|
|
|
|
|
As this test takes significantly more time than the other end-to-end tests,
set a suitable default value for the configuration variable TIMEOUT_SCALE.
|
|
|
|
|
|
While there, fix a typo in the setup.
|
|
... verifying the consistency of the representation of trees between
local and remote CAS.
|
|
|
|
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.
|
|
... also verifying that the local CAS is used, even in the presence
of remote execution.
|
|
... and, in this way, ensure the test also tests properly in
absence of an external remote execution system.
|
|
|
|
... so that we can switch in one go and have all tests use a new
just-mr tool, e.g., once we consider the C++ implementation fully
ready. This single point of switch will be relevant as the next
commit will add the first end-to-end test for just-mr itself.
|
|
|
|
|
|
|