[CT] Cleanup chromium builds from GCS after the run completes
They were stored incase we needed the build for any reason. I do not
think it has ever been useful and takes up unnecessary space.
pixel_diff_on_workers/main.go already does this.
Bug: skia:8670
Change-Id: If016e433e702085f811adb286f5a8003c96039c2
Reviewed-on: https://skia-review.googlesource.com/c/183243
Reviewed-by: Ben Wagner <benjaminwagner@google.com>
Commit-Queue: Ravi Mistry <rmistry@google.com>
diff --git a/ct/go/master_scripts/run_chromium_analysis_on_workers/main.go b/ct/go/master_scripts/run_chromium_analysis_on_workers/main.go
index fdb1345..bbf580a 100644
--- a/ct/go/master_scripts/run_chromium_analysis_on_workers/main.go
+++ b/ct/go/master_scripts/run_chromium_analysis_on_workers/main.go
@@ -220,6 +220,9 @@
return
}
+ // Clean up the chromium builds from Google storage after the run completes.
+ defer gs.DeleteRemoteDirLogErr(filepath.Join(util.CHROMIUM_BUILDS_DIR_NAME, chromiumBuild))
+
// Archive, trigger and collect swarming tasks.
isolateExtraArgs := map[string]string{
"CHROMIUM_BUILD": chromiumBuild,
diff --git a/ct/go/master_scripts/run_chromium_perf_on_workers/main.go b/ct/go/master_scripts/run_chromium_perf_on_workers/main.go
index 94b9111..6fefb04 100644
--- a/ct/go/master_scripts/run_chromium_perf_on_workers/main.go
+++ b/ct/go/master_scripts/run_chromium_perf_on_workers/main.go
@@ -244,6 +244,10 @@
return
}
+ // Clean up the chromium builds from Google storage after the run completes.
+ defer gs.DeleteRemoteDirLogErr(filepath.Join(util.CHROMIUM_BUILDS_DIR_NAME, chromiumBuildNoPatch))
+ defer gs.DeleteRemoteDirLogErr(filepath.Join(util.CHROMIUM_BUILDS_DIR_NAME, chromiumBuildWithPatch))
+
// Archive, trigger and collect swarming tasks.
isolateExtraArgs := map[string]string{
"CHROMIUM_BUILD_NOPATCH": chromiumBuildNoPatch,
