)]}'
{
  "commit": "b995ff63d8a427be733e7094e96fbbc67c8ac850",
  "tree": "d9a593965c124ae6132c370d300e6b0f290ba1c6",
  "parents": [
    "f19647824bd63c89ddbcad245f1b8635dbee7138"
  ],
  "author": {
    "name": "gurusai-voleti",
    "email": "gvoleti@google.com",
    "time": "Mon Apr 27 12:23:19 2026 +0000"
  },
  "committer": {
    "name": "fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Apr 28 12:32:15 2026 -0700"
  },
  "message": "Automated: Migrate fuchsia/libc-tests from gsutil to gcloud storage\n\nThis CL is part of the on going effort to migrate from the legacy \"gsutil\" tool to the new and improved \"gcloud storage\" command-line interface.\n\"gcloud storage\" is the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with other \"gcloud\" components. 🚀\n\n⚠️ Action Required: Please Review and Test Carefully:\n\nWhile we have based the automation on the migration guide, every use case is unique.\n\"IT IS CRUCIAL that you THOROUGHLY TEST these changes in environments appropriate to your use-case BEFORE MERGING.\"\nBe aware of potential differences between \"gsutil\" and `gcloud storage` that could impact your workflows.\nFor instance, the structure of command output may have changed, requiring updates to any scripts that parse it. Similarly, command behavior can differ subtly; the \"gcloud storage rsync\" command has a different file deletion logic than \"gsutil rsync\", which could lead to unintended file deletions.\n\nOur migration guides can help guide you through a list of mappings and some notable differences between the two tools.\n\nStandard presubmit tests are run as part of this CL\u0027s workflow. \"If you need to target an ADDITIONAL TEST WORKFLOW or REQUIRE ASSISTANCE WITH TESTING, please let us know.\"\n\nPlease verify that all your Cloud Storage operations continue to work as expected to avoid any potential disruptions in production.\nAutomation Details:\n\nThis change was GENERATED AUTOMATICALLY by an agent that targets users of \"gsutil\".\nThe transformations applied are based on the gsutil to gcloud storage migration guide - http://go/gsutil-gcloud-storage-migration-guide, external guide - https://docs.cloud.google.com/storage/docs/gsutil-transition-to-gcloud.\n\nSupport and Collaboration:\n\nThe \"GCS CLI\" team is here to help! If you encounter any issues, have a complex use case that this automated change doesn\u0027t cover, or face any other blockers, please don\u0027t hesitate to reach out.\nWe are happy to work with you to test and adjust these changes as needed.\n\nContact: gcs-cli-hyd@google.com\n\nWe appreciate your partnership in this important migration effort!\nBUG: b:486536908\n\nChange-Id: If69e6d5fc150debec69f82c382ddc266fe6ef6f1\nReviewed-on: https://fuchsia-review.googlesource.com/c/libc-tests/+/1590129\nReviewed-by: Roland McGrath \u003cmcgrathr@google.com\u003e\nCommit-Queue: Roland McGrath \u003cmcgrathr@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "96b623b4231daae44bf09c0eb72de4835cf37871",
      "old_mode": 33261,
      "old_path": "third_party/nacl-tests/abi_corpus/corpus_utils.py",
      "new_id": "41acd5055e1c478ec7feb1bcb9a7cd78b0e1198a",
      "new_mode": 33261,
      "new_path": "third_party/nacl-tests/abi_corpus/corpus_utils.py"
    }
  ]
}