Make the check for the sanity of install_base_key more stringent.

A previous commit caused install_base_key to be a large .zip file instead of 32 alphanumeric characters. Thus, when Bazel tried to extract itself, it tried to create a directory of the name "$INSTALL_BASE/<40M path segment>/<long path>", and it allocated said 40M each time it walked up a path segment trying to create parent directories.

--
MOS_MIGRATED_REVID=105600489

1 files changed, 3 insertions, 2 deletions

diff --git a/src/main/cpp/blaze.cc b/src/main/cpp/blaze.cc
index 1e051b6a2c..02682115b9 100644
--- a/src/main/cpp/blaze.cc
+++ b/src/main/cpp/blaze.cc
@@ -189,9 +189,10 @@ class GetInstallKeyFileProcessor : public devtools_ijar::ZipExtractorProcessor {
                        const devtools_ijar::u1 *data, const size_t size) {
     string str(reinterpret_cast<const char *>(data), size);
     blaze_util::StripWhitespace(&str);
-    if (str.size() < 32) {
+    if (str.size() != 32) {
       die(blaze_exit_code::LOCAL_ENVIRONMENTAL_ERROR,
-          "\nFailed to extract install_base_key: file too short");
+          "\nFailed to extract install_base_key: file size mismatch "
+          "(should be 32, is %zd)", str.size());
     }
     *install_base_key_ = str;
   }