PSA: Tast always build remote bundles in chroot
Seewai Fu
TL;DR
Tast will always build remote bundles in chroot even if -build=false flag is set. There is no change in how Tast handles local bundles.
Background
The Tast remote private bundles are no longer populated in chroot (cros_sdk). As a result, Tast cannot run private tests (local or remote) if -build=false is set. With the current Tast architecture, local bundles are driven by corresponding remote bundles. If -build=true flag is used, it will continue to work because Tast will build the specified bundles. However, it will be an issue with -build=false flag because there are no private remote bundles in the /usr/libexec/tast/remote to drive the corresponding local bundles inside. Since CFT does not use chroot, most CQs and release builders are not affected by the issue.
Always Build Remote Bundles
To address this issue, this CL made Tast always build all remote (public or private) bundles when the -build=true flag is used inside chroot. There is no change for the handling of local bundles. Tast continue to download private local bundles when the -build=true and -downloadprivatebundles=true flags are used.
Contact
If you encounter any issues, please contact Tast team: tast...@google.com.
Seewai Fu
TL;DR
Tast will always build remote bundles in chroot even if -build=false flag is set. There is no change in how Tast handles local bundles.
Background
The Tast remote private bundles are no longer populated in chroot (cros_sdk). As a result, Tast cannot run private tests (local or remote) if -build=false is set. With the current Tast architecture, local bundles are driven by corresponding remote bundles. If -build=true flag is used, it will continue to work because Tast will build the specified bundles. However, it will be an issue with -build=false flag because there are no private remote bundles in the /usr/libexec/tast/remote to drive the corresponding local bundles inside. Since CFT does not use chroot, most CQs and release builders are not affected by the issue.
Always Build Remote Bundles
To address this issue, this CL made Tast always build all remote (public or private) bundles when the -build=false flag is used inside chroot. There is no change for the handling of local bundles. Tast continue to download private local bundles when the -build=false and -downloadprivatebundles=true flags are used.