autoroller: Always roll and improve description

autoroller: Always roll and improve description

In order to minimize bisection ranges when the roll breaks, we want
to update the chromium_revision as often as possible.
Even if a roll doesn't bring in changed dependencies or Clang version,
it still brings in changes in the Chromium build toolchain.

The description now contains links to all dependencies that change
(if any).

BUG=webrtc:4688
R=phoglund@webrtc.org

Committed: https://crrev.com/a9c584d4652641707f4b7abefaa3acdb1bc5866f
Cr-Commit-Position: refs/heads/master@{#10141}

[kjellander_webrtc, 2015-10-01 17:05:18]

kjellander@webrtc.org changed reviewers:
+ phoglund@webrtc.org

[kjellander_webrtc, 2015-10-01 17:05:18]

With this CL, the commit message of
https://chromium.googlesource.com/external/webrtc/+/edba998cf16f500e258d25149...
would look like this (except the manually modified parts):

Roll chromium_revision 8cf53d6..7849253 (351112:351822)

Change log: https://chromium.googlesource.com/chromium/src/+log/8cf53d6..7849253
Full diff: https://chromium.googlesource.com/chromium/src/+/8cf53d6..7849253

Changed dependencies:
* src/buildtools:
https://chromium.googlesource.com/chromium/buildtools.git/+log/8d89c1b..0c88009
* src/third_party/boringssl/src:
https://boringssl.googlesource.com/boringssl.git/+log/4c60d35..8c9b878
* src/third_party/libvpx_new/source/libvpx:
https://chromium.googlesource.com/webm/libvpx.git/+log/90a109f..7d28d12
* src/third_party/libyuv:
https://chromium.googlesource.com/libyuv/libyuv.git/+log/62c49dc..d039ad6
* src/third_party/openmax_dl:
https://chromium.googlesource.com/external/webrtc/deps/third_party/openmax.gi...
DEPS diff:
https://chromium.googlesource.com/chromium/src/+/8cf53d6..7849253/DEPS

Clang version was not updated in this roll.

[phoglund, 2015-10-02 06:53:43]

lgtm

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
File tools/autoroller/roll_chromium_revision.py (right):

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
tools/autoroller/roll_chromium_revision.py:397: current_git_number =
ParseCommitPosition(ReadRemoteCrCommit(current_cr_rev))
Nit: current_git_pos or current_commit_pos? That introduces less concepts than
if we're talking about both git numbers and git commit positions.

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
tools/autoroller/roll_chromium_revision.py:398: new_git_number =
ParseCommitPosition(ReadRemoteCrCommit(new_cr_rev))
Ditto

[kjellander_webrtc, 2015-10-02 07:10:37]

Comments adressed.

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
File tools/autoroller/roll_chromium_revision.py (right):

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
tools/autoroller/roll_chromium_revision.py:397: current_git_number =
ParseCommitPosition(ReadRemoteCrCommit(current_cr_rev))
On 2015/10/02 06:53:42, phoglund wrote:
> Nit: current_git_pos or current_commit_pos? That introduces less concepts than
> if we're talking about both git numbers and git commit positions.

Good idea, I incorporated it in PS#3.

https://codereview.webrtc.org/1381963003/diff/20001/tools/autoroller/roll_chr...
tools/autoroller/roll_chromium_revision.py:398: new_git_number =
ParseCommitPosition(ReadRemoteCrCommit(new_cr_rev))
On 2015/10/02 06:53:42, phoglund wrote:
> Ditto

Done.

[kjellander_webrtc, 2015-10-02 07:12:14]

Committed patchset #3 (id:40001) manually as
a9c584d4652641707f4b7abefaa3acdb1bc5866f (presubmit successful).

[commit-bot: I haz the power, 2015-10-02 07:12:17]

Patchset 3 (id:??) landed as
https://crrev.com/a9c584d4652641707f4b7abefaa3acdb1bc5866f
Cr-Commit-Position: refs/heads/master@{#10141}