Age | Commit message (Collapse) | Author |
|
serve_target_remote_build.sh should be updated once just-serve can
orchestrate the remote build
|
|
... by renaming test/end-to-end/targets.
|
|
... verifying that deduplication does not modify the analysis
result.
|
|
Before this patch, when creating an action directory, symlinks were
staged as regular files.
|
|
|
|
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.
|
|
Co-authored by: Klaus Aehlig <klaus.aehlig@huawei.com>
|
|
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.
|
|
... to avoid potential staging conflicts. Having them staged to
just-mr was a copy-and-paste error in the first place anyway.
|
|
|
|
in the end-to-end tests
|
|
... and, instead, stores all needed information in git and
CAS-independent index files.
|
|
... 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.
|
|
|
|
... also when determining default module or target.
|
|
|
|
|
|
Before this patch, the built-in "generic" type allowed for just output
files, listed in the field "outs". Now, the type also supports output
directories, listed in the "out_dirs" field. The output directories
are created before the command is executed.
|
|
... allowing to provide additional information in case of conflict
during flat staging.
|
|
|
|
... in particular verifying that relative references cannot go
outside a repository and explict file ferences cannot go upwards.
|
|
This test also demonstrates the notion of equality used in our
action graph: actions are considered equal, if they are defined in
the same way (regardless of where they are defined); when looking up
actions in cache, however, the inputs are considered extensionally.
The test also verifies that if one dumps the action graph, the
origins of an action (as the same action can be defined in many
places) are reported correctly.
|