Google Git
Sign in
cos / mirrors / cros / chromiumos / third_party / toolchain-utils / 16d12146ddf8c2ea77f12dbc43bf6ab55d742d80
commit16d12146ddf8c2ea77f12dbc43bf6ab55d742d80[log] [tgz]
authorGeorge Burgess IV <gbiv@google.com>Tue Apr 28 12:58:35 2020 -0700
committerGeorge Burgess <gbiv@chromium.org>Tue Apr 28 20:11:20 2020 +0000
treed2595f457ab9467972797914ad0e0db0478aa2bc
parentded113a1f5e9d2715361d8e2836edd0c48925d15 [diff]
llvm_tools: don't check the same SHA for reverts twice

It occurred to me that there are times where llvm-next == llvm-stable.
If that's the case, we shouldn't generate two emails with (nearly)
identical contents.

BUG=chromium:1046988
TEST=unittests

Change-Id: Ib19db46daf95e73c64cc958d57c4220fc957bb51
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2171297
Reviewed-by: Tiancong Wang <tcwang@google.com>
Tested-by: George Burgess <gbiv@chromium.org>
1 file changed
tree: d2595f457ab9467972797914ad0e0db0478aa2bc
  1. afdo_metadata/
  2. afdo_redaction/
  3. afdo_tools/
  4. android_bench_suite/
  5. bestflags/
  6. binary_search_tool/
  7. compiler_wrapper/
  8. cros_utils/
  9. crosperf/
  10. cwp/
  11. debug_info_test/
  12. go/
  13. heatmaps/
  14. llvm_extra/
  15. llvm_tools/
  16. orderfile/
  17. pgo_tools/
  18. toolchain_utils_githooks/
  19. .gitignore
  20. .style.yapf
  21. android_merge_from_upstream.sh
  22. auto_delete_nightly_test_data.py
  23. build_chromeos.py
  24. build_tc.py
  25. buildbot_test_llvm.py
  26. buildbot_test_toolchains.py
  27. chromiumos_image_diff.py
  28. compiler-test.sh
  29. file_lock_machine.py
  30. file_lock_machine_test.py
  31. image_chromeos.py
  32. LICENSE
  33. lock_machine.py
  34. OWNERS
  35. OWNERS.toolchain
  36. PRESUBMIT.cfg
  37. pyrun
  38. README.chromium
  39. README.md
  40. remote_test.py
  41. run_tests_for.py
  42. setup_chromeos.py
  43. tc_enter_chroot.py
  44. update_telemetry_defaults.py
README.md

toolchain-utils

Various utilities used by the Chrome OS toolchain team.

Note

To run Python scripts in this directory, first run:

export PYTHONPATH=$(readlink -f .):$PYTHONPATH

from this directory.

Then you can run any script.

To get help on any script, type in python <script> --help, or refer to the header of the script for more information.