mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-10 12:09:31 +00:00
build-chromeos.sh: Clean up cros repo after build
Kokoro will treat the files as build artifacts and tries to rsync the ~80GB to the executor. See b/30309837. BUG=b:2089374426 TEST=None Change-Id: I71df011025a7cff664a134bdfbf5783709365358 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3611872 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
This commit is contained in:
parent
2c4f981ae4
commit
4ebb928ea4
1 changed files with 9 additions and 0 deletions
|
@ -65,6 +65,15 @@ build_and_test_crosvm() {
|
|||
time cros_sdk cros_run_unit_tests --board "$BOARD" --packages "${PACKAGE_LIST[@]}"
|
||||
}
|
||||
|
||||
cleanup_cros() {
|
||||
# Delete cros repo to prevent it from being treated as a build artifact by Kokoro.
|
||||
cros_sdk --delete || true
|
||||
sudo rm -rf "${CROS_ROOT}" || true
|
||||
# Call original cleanup function from common.sh
|
||||
cleanup
|
||||
}
|
||||
trap cleanup_cros EXIT
|
||||
|
||||
main() {
|
||||
mkdir -p "$CROS_ROOT"
|
||||
cd "$CROS_ROOT"
|
||||
|
|
Loading…
Reference in a new issue