Fix regression of mktree not always rebuilding #2726
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Commit d4e808e added cmake caching for mktree so that we don't rebuild the tree on each "make check" invocation. However, this means we can now easily miss some test dependencies being updated since we don't depend on everything, e.g. the data/ dir.
To fix this, instead of adding each and every file and directory as a dependency of the mktree.output command, just rebuild the tree every time. The base image (made with DNF) is already cached anyway, and the added overhead is tiny and outweighs the (potential) engineering hours lost due to this.
The funny thing is, this was already fixed once in 2019: fc05045
Sometimes you've just gotta fix stuff twice before it sticks!
Fixes: #2725