Clarify output from bisect-builds so that it's more clear what the

tools/bisect-builds.py

Index: tools/bisect-builds.py
===================================================================
--- tools/bisect-builds.py	(revision 132659)
+++ tools/bisect-builds.py	(working copy)
@@ -29,6 +29,9 @@
 WEBKIT_CHANGELOG_URL = 'http://trac.webkit.org/log/' \
                        'trunk/?rev=%d&stop_rev=%d&verbose=on'
 
+DONE_MESSAGE = 'You are probably looking for a change made after ' \
+               '%d (known good), but no later than %d (first known bad).'
+
 ###############################################################################
 
 import math
@@ -542,15 +545,16 @@
     last_known_good_webkit_rev, first_known_bad_webkit_rev = 0, 0
 
   # We're done. Let the user know the results in an official manner.
-  print('You are probably looking for build %d.' % first_known_bad_rev)
+  print DONE_MESSAGE % (last_known_good_rev, first_known_bad_rev)
+  print 'All Chromium changes on one page:'
+  print '  ' + CHANGELOG_URL % (last_known_good_rev, first_known_bad_rev)
   if last_known_good_webkit_rev != first_known_bad_webkit_rev:
-    print 'WEBKIT CHANGELOG URL:'
-    print WEBKIT_CHANGELOG_URL % (first_known_bad_webkit_rev,
-                                  last_known_good_webkit_rev)
-  print 'CHANGELOG URL:'
-  print CHANGELOG_URL % (last_known_good_rev, first_known_bad_rev)
-  print 'Built at revision:'
-  print BUILD_VIEWVC_URL % first_known_bad_rev
+    print 'All WebKit changes on one page:'
+    print '  ' + WEBKIT_CHANGELOG_URL % (first_known_bad_webkit_rev,
+                                         last_known_good_webkit_rev)
+  print 'All possible Chromium revisions to investigate:'
+  for rev in range(last_known_good_rev + 1, first_known_bad_rev + 1):
+    print '  ' + BUILD_VIEWVC_URL % rev

[Nico, 2012/04/17 22:04:53]

The scrollback from this will push the more interesting all-in-one-page urls too
far up I think.

 
 
 if __name__ == '__main__':