Commit 5b753f47 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/devtools-frontend/src 7eee1a626bd1..80a89976c142 (1 commits)

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/7eee1a626bd1..80a89976c142

git log 7eee1a626bd1..80a89976c142 --date=short --no-merges --format='%ad %ae %s'
2019-11-08 yangguo@chromium.org Simplify build

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@80a89976c142

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC v8-waterfall-sheriff@grotations.appspotmail.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/+/master/autoroll/README.md

TBR=v8-waterfall-sheriff@grotations.appspotmail.com

Bug: None
Change-Id: I6082e6fa1d9fecd32a369126a4531121929c0e19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906714Reviewed-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@{#713960}
parent ef2ab531
......@@ -243,7 +243,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling devtools-frontend
# and whatever else without interference from each other.
'devtools_frontend_revision': '7eee1a626bd162ff8eaa017c6a1f94a83613b6c3',
'devtools_frontend_revision': '80a89976c1420ca7cc12b6e4702cefb0eb7bfc29',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libprotobuf-mutator
# 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