Docserver: Make broken link integration test warning more visible.

Moved the broken link integration test rebasing call to action to the bottom and made the warning more visible.

NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=244543

[dhnishi (use Chromium), 2013-12-16 21:09:42]

@kalman: I didn't rebase the broken link detection after r240763, so I'm
rebasing it here.

I missed the warning about it during the presubmit because it was in the middle
after the list of the 52 orphaned pages. To remedy that, I moved the warning
down to the bottom after all of the link error tests and made it more visible
like the YAML warning.

[not at google - send to devlin, 2013-12-17 20:22:37]

lgtm

https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/server2/integration_test.py (right):

https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/server2/integration_test.py:87: print('The broken
links are:')
maybe leave out this print

https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/server2/integration_test.py:173: print('Found %s
broken links, but there were no changes.' %
This message has bugged me. Can you change it to '%s existing broken links' %
len(broken_links)

[dhnishi (use Chromium), 2014-01-10 20:55:26]

On 2013/12/17 20:22:37, kalman wrote:
> lgtm
> 
>
https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
> File chrome/common/extensions/docs/server2/integration_test.py (right):
> 
>
https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
> chrome/common/extensions/docs/server2/integration_test.py:87: print('The
broken
> links are:')
> maybe leave out this print
> 
>
https://codereview.chromium.org/111643007/diff/20001/chrome/common/extensions...
> chrome/common/extensions/docs/server2/integration_test.py:173: print('Found %s
> broken links, but there were no changes.' %
> This message has bugged me. Can you change it to '%s existing broken links' %
> len(broken_links)

Since this test is currently disabled, should I revise the patch to have the
changes to the integration test and commented out, or wait until the test is
re-enabled?

[not at google - send to devlin, 2014-01-10 21:03:26]

might as well submit it. eventually we should actually reenable the test but I
don't know what it will take. perhaps we need to be smart and strip the contents
things out (only test them once)?

[commit-bot: I haz the power, 2014-01-13 18:52:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/DHNishi@gmail.com/111643007/130001

[commit-bot: I haz the power, 2014-01-13 18:54:50]

Change committed as 244543