Commit d1fe7c5a authored by Alexei Svitkine's avatar Alexei Svitkine Committed by Commit Bot

Point at a different bug from variations presubmit.

Pointing at the other bug was confusing, because it's
state was unclear about next steps.

Bug: 1053702
Change-Id: Ia885dc21f028aabe150d55e74d927f3a37c8a371
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063331
Auto-Submit: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: default avatarRobert Kaplow <rkaplow@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742666}
parent bb767b72
...@@ -26,7 +26,8 @@ FIELDTRIAL_CONFIG_TOO_LONG_ERROR_MSG = \ ...@@ -26,7 +26,8 @@ FIELDTRIAL_CONFIG_TOO_LONG_ERROR_MSG = \
"entries. To check if an entry is obsolete, do a code search for its "\ "entries. To check if an entry is obsolete, do a code search for its "\
"'enable_features' and 'disable_features' strings and verify there are "\ "'enable_features' and 'disable_features' strings and verify there are "\
"no results other than the files related to the testing config. "\ "no results other than the files related to the testing config. "\
"See crbug.com/1045530 for more details." % FIELDTRIAL_CONFIG_FILE_NAME "Automating this is tracked under crbug.com/1053702." % \
FIELDTRIAL_CONFIG_FILE_NAME
def PrettyPrint(contents): def PrettyPrint(contents):
......
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