Commit 6b6c518d authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Catapult from cd6894f0a29e to bbbe9134378d (1 revision)

https://chromium.googlesource.com/catapult.git/+log/cd6894f0a29e..bbbe9134378d

2020-06-02 bpastene@chromium.org devil: Remove special EBUSY error logging when mkdir'ing on devices

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC wenbinzhang@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:739899
Tbr: wenbinzhang@google.com
Change-Id: Ic5194f779e084d7255796fac4396b738d391a33e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227274Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#774414}
parent 740d8890
......@@ -241,7 +241,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling catapult
# and whatever else without interference from each other.
'catapult_revision': 'cd6894f0a29e6f33767f14d17e34243093987e52',
'catapult_revision': 'bbbe9134378dd6b9f8284e52d16628d0920f71b1',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libFuzzer
# and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment