[release] Let release script fix missing tags.

[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.

Committed: https://crrev.com/6fe3387778cc1829f89c90bf11a9532fb42fb578
Cr-Commit-Position: refs/heads/master@{#35437}

[Michael Achenbach, 2016-04-13 08:14:56]

Description was changed from

==========
[release] Let release script fix missing tags.

BUG=
==========

to

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.


BUG=
==========

[Michael Achenbach, 2016-04-13 08:14:56]

machenbach@chromium.org changed reviewers:
+ hablich@chromium.org

[Michael Achenbach, 2016-04-13 08:15:39]

PTAL. Didn't add a test for that case as it'd be quite huge.

[Michael Hablich, 2016-04-13 09:36:07]

Description was changed from

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.


BUG=
==========

to

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.
==========

[Michael Hablich, 2016-04-13 09:37:47]

On 2016/04/13 08:15:39, Michael Achenbach wrote:
> PTAL. Didn't add a test for that case as it'd be quite huge.

lgtm, thanks.

I removed the bug reference btw.

[Michael Hablich, 2016-04-13 09:37:50]

The CQ bit was checked by hablich@chromium.org

[commit-bot: I haz the power, 2016-04-13 09:37:58]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1887583002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1887583002/1

[commit-bot: I haz the power, 2016-04-13 09:59:59]

Description was changed from

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.
==========

to

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.
==========

[commit-bot: I haz the power, 2016-04-13 10:00:00]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-13 10:01:24]

Description was changed from

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.
==========

to

==========
[release] Let release script fix missing tags.

Check if a previous run left an inconsistent state behind.
The check is right before trying to push a new state as then
all information is available, like commit message and tag
name.

This is still only a band-aid. If gnumbd is down for a
longer period, an unprocessed commit won't be found, but
the push attempt will still fail.

Committed: https://crrev.com/6fe3387778cc1829f89c90bf11a9532fb42fb578
Cr-Commit-Position: refs/heads/master@{#35437}
==========

[commit-bot: I haz the power, 2016-04-13 10:01:25]

Patchset 1 (id:??) landed as
https://crrev.com/6fe3387778cc1829f89c90bf11a9532fb42fb578
Cr-Commit-Position: refs/heads/master@{#35437}