abderrahim opened a new issue, #1983:
URL: https://github.com/apache/buildstream/issues/1983
Currently, remote caches are initialized pretty early in the buildstream
start sequence. At least for `checkout` operations, this is often too early to
know whether the caches are actually needed.
There are a few situations:
* target directory is not empty: Loading elements -> Resolving elements ->
Initializing remote caches -> target directory is not empty
* this wastes time before reporting the error
* artifacts are cached locally: Loading elements -> Resolving elements ->
Initializing remote caches -> Query cache -> Staging dependencies ->
Integrating sandbox -> Checking out files
* We don't need remote caches here, so it also wastes time
* artifacts aren't cached: Loading elements -> Resolving elements ->
Initializing remote caches -> Query cache -> Attempting to fetch missing or
incomplete artifact(s) ...
* This is the case that needs initializing remote caches. However it makes
more sense to do it after the "Attempting to fetch", not before.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
