Google Git
Sign in
chromium/catapult/f3756001f32ddbfb690c0fd854519bc4583c50a1
commit
f3756001f32ddbfb690c0fd854519bc4583c50a1
[log]
author
Ben Pastene <bpastene@chromium.org>
Fri May 08 19:37:23 2026
committer
catapult-scoped@luci-project-accounts.iam.gserviceaccount.com <catapult-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri May 08 20:51:28 2026
tree
af9548382a7a980dd51e4cd852c97c0ee8b91254
parent
092af042dd02eb3381ce3b647004314482b2d4e3 [diff]
Fix gsutil path when pulling it from depot_tools on windows

https://crrev.com/c/7667499 works for linux, but not windows. This is
because we were passing the batch file version of depot_tool's gsutil
to python:
https://chromium.googlesource.com/chromium/tools/depot_tools/+/refs/heads/main/gsutil.py.bat
vs
https://chromium.googlesource.com/chromium/tools/depot_tools/+/refs/heads/main/gsutil.py

This should fix that.

Bug: chromium:492147922
Change-Id: Ia75eb5171d35ed062687643ef0f4282a3e98b5c5
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/7833117
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
1 file changed
tree: af9548382a7a980dd51e4cd852c97c0ee8b91254
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. hooks/
  10. infra/
  11. netlog_viewer/
  12. perf_issue_service/
  13. skia_bridge/
  14. systrace/
  15. telemetry/
  16. third_party/
  17. trace_processor/
  18. tracing/
  19. .eslintignore
  20. .eslintrc
  21. .gcloudignore
  22. .gitignore
  23. .gitmodules
  24. .style.yapf
  25. .vpython3
  26. .yapfignore
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. CONTRIBUTING.md
  31. DEPS
  32. DIR_METADATA
  33. generate_telemetry_build.py
  34. LICENSE
  35. navbar.md
  36. OWNERS
  37. PRESUBMIT.py
  38. pylintrc
  39. README.md
  40. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide