Update style according to advice from pylint.

tools/auto_bisect/bisect_printer.py

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 """This file contains printing-related functionality of the bisect."""
 
 import datetime
 import re
 
 from bisect_results import BisectResults
@@ skipping 19 matching lines @@
 RESULTS_REVISION_INFO = """
 ===== SUSPECTED CL(s) =====
 Subject : %(subject)s
 Author  : %(author)s%(commit_info)s
 Commit  : %(cl)s
 Date    : %(cl_date)s"""
 
 RESULTS_THANKYOU = """
 | O O | Visit http://www.chromium.org/developers/core-principles for Chrome's
 |  X  | policy on perf regressions. Contact chrome-perf-dashboard-team with any
-| / \ | questions or suggestions about bisecting. THANK YOU."""
+| / \\ | questions or suggestions about bisecting. THANK YOU."""

[Sergiy Byelozyorov, 2014/10/30 11:42:45]

Another tooth? Please align face boundaries :-).

[qyearsley, 2014/10/30 16:46:04]

This is actually the same as before -- """\ """ is the same as """\\ """. In
both cases it's a backslash followed by a space. But, if the character following
the backslash was another character, e.g. a "t", then it would be different, so
that's why pylint suggests representing all backslashes as \\.

 
 REPRO_STEPS_LOCAL = """
 ==== INSTRUCTIONS TO REPRODUCE ====
 To run locally:
  - Use the test command given under 'BISECT JOB RESULTS' above.
  - Consider using a profiler. Pass --profiler=list to list available profilers.
 """
 
 REPRO_STEPS_TRYJOB = """
 To reproduce on a performance try bot:
@@ skipping 328 matching lines @@
 
   @staticmethod
   def _PrintWarnings(warnings):
     """Prints a list of warning strings if there are any."""
     if not warnings:
       return
     print
     print 'WARNINGS:'
     for w in set(warnings):
       print '  ! %s' % w