Update Dr. Memory to 0x4c19296, (release 1.10.0)

Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=

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

[zhaoqin1, 2016-03-17 00:19:16]

The CQ bit was checked by zhaoqin@chromium.org

[commit-bot: I haz the power, 2016-03-17 00:19:38]

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

[commit-bot: I haz the power, 2016-03-17 00:19:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-17 00:19:40]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[zhaoqin1, 2016-03-17 00:27:28]

Description was changed from

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org
BUG=
==========

to

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=
==========

[zhaoqin1, 2016-03-17 00:27:28]

zhaoqin@chromium.org changed reviewers:
+ oshima@chromium.org

[oshima, 2016-03-17 01:02:27]

not sure if this help, but lgtm

[oshima, 2016-03-17 01:02:33]

The CQ bit was checked by oshima@chromium.org

[commit-bot: I haz the power, 2016-03-17 01:03:02]

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

[commit-bot: I haz the power, 2016-03-17 01:45:51]

Description was changed from

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=
==========

to

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=
==========

[commit-bot: I haz the power, 2016-03-17 01:45:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-17 01:47:21]

Description was changed from

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=
==========

to

==========
Update Dr. Memory to 0x4c19296, (release 1.10.0)

TBR=bruening@chromium.org, oshima@chromium.org
BUG=

Committed: https://crrev.com/b8b45d19a6322d1d022c491e8813ee4ed252663c
Cr-Commit-Position: refs/heads/master@{#381635}
==========

[commit-bot: I haz the power, 2016-03-17 01:47:22]

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

[oshima, 2016-03-17 16:10:28]

On 2016/03/17 01:47:22, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/b8b45d19a6322d1d022c491e8813ee4ed252663c
> Cr-Commit-Position: refs/heads/master@{#381635}

Is there anything else that we need to do to deploy new version to bots?
Bots still have errors after this.
(https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%2...)

[brucedawson, 2016-03-17 18:55:36]

On 2016/03/17 16:10:28, oshima wrote:
> On 2016/03/17 01:47:22, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/b8b45d19a6322d1d022c491e8813ee4ed252663c
> > Cr-Commit-Position: refs/heads/master@{#381635}
> 
> Is there anything else that we need to do to deploy new version to bots?
> Bots still have errors after this.
>
(https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%2...)

We have to roll DEPS to get Chromium to use the new version. I can take a look
at doing that.

[brucedawson, 2016-03-17 19:38:55]

> We have to roll DEPS to get Chromium to use the new version. I can take a look
> at doing that.

Ignore my last comment. third_party\chromium is in the Chromium repo so no DEPS
roll is needed. Testing.

[chromium-reviews, 2016-03-17 21:08:44]

I think that's all for updating dr. memory, we need debug those failures
and errors to figure out why.
On Mar 17, 2016 12:10 PM, <oshima@chromium.org> wrote:

> On 2016/03/17 01:47:22, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/b8b45d19a6322d1d022c491e8813ee4ed252663c
> > Cr-Commit-Position: refs/heads/master@{#381635}
>
> Is there anything else that we need to do to deploy new version to bots?
> Bots still have errors after this.
> (
>
https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%2...
> )
>
> https://codereview.chromium.org/1808023003/
>

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.