| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
...with explicit std::unordered_set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As only a recent commit made it possible to rotate the repository
cache more than once, add a test ensuring two properties.
- Repeated repository gc is possible and roots are taken from the
rotated generation.
- It is possible to fully rotate a root out.
|
|
|
|
|
|
While our tool promises to generate a reproducible order of the
action origins, we should not insist on a particular one. Therefore
sort before comparing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This avoids the tool accidentally trying to touch the home folder
via the default cache location.
While there, ensure that errors in just-lock calls trigger test
failures, as it should be.
|
|
|
|
... allowing to print the unique artifact built (if any). This
allows convenient inspection of the build result of targets that
define precisely one artifact.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It used to be the case, that the option -P was forwarded to
the build of computed roots. Add a test verifying we're not
regressing there again.
|
|
|
|
|
|
|
|
|
|
|
|
|
