Add microdump_stackwalk target to chromium.android builders.

Add microdump_stackwalk target to chromium.android builders.

This will allow the testers to symbolize microdump crash logs.

BUG=593106
Review-Url: https://codereview.chromium.org/2724273003
Cr-Commit-Position: refs/heads/master@{#455516}
Committed: https://chromium.googlesource.com/chromium/src/+/37fc2c0e956c32dda663bc7c3e93bdf16779b35d

[mikecase (-- gone --), 2017-03-02 22:19:46]

mikecase@chromium.org changed reviewers:
+ bpastene@chromium.org, martiniss@chromium.org

[martiniss, 2017-03-02 22:58:07]

lgtm

I'm not sure if this will break anything.

bpastene might be more confident this won't

[bpastene, 2017-03-03 19:30:17]

lgtm

[mikecase (-- gone --), 2017-03-07 00:17:45]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2017-03-07 00:18:30]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-07 01:46:28]

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

[commit-bot: I haz the power, 2017-03-07 01:46:29]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[mikecase (-- gone --), 2017-03-07 23:39:53]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2017-03-07 23:40:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-08 02:34:03]

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

[commit-bot: I haz the power, 2017-03-08 02:34:04]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[mikecase (-- gone --), 2017-03-08 17:17:33]

Ok, no idea why windows bot keep failing. Theres no way this CL caused it so
going to try again.

[mikecase (-- gone --), 2017-03-08 17:17:36]

The CQ bit was checked by mikecase@chromium.org

[commit-bot: I haz the power, 2017-03-08 17:18:02]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-08 19:39:20]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488993456005180, "parent_rev":
"2bc5b5fb3da0c205a025535faff4fb160ca6467a", "commit_rev":
"37fc2c0e956c32dda663bc7c3e93bdf16779b35d"}

[commit-bot: I haz the power, 2017-03-08 19:40:02]

Description was changed from

==========
Add microdump_stackwalk target to chromium.android builders.

This will allow the testers to symbolize microdump crash logs.

BUG=593106
==========

to

==========
Add microdump_stackwalk target to chromium.android builders.

This will allow the testers to symbolize microdump crash logs.

BUG=593106

Review-Url: https://codereview.chromium.org/2724273003
Cr-Commit-Position: refs/heads/master@{#455516}
Committed:
https://chromium.googlesource.com/chromium/src/+/37fc2c0e956c32dda663bc7c3e93...
==========

[commit-bot: I haz the power, 2017-03-08 19:40:03]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/37fc2c0e956c32dda663bc7c3e93...

[mikecase (-- gone --), 2017-03-08 21:25:15]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2734423002/ by mikecase@chromium.org.

The reason for reverting is: So, needed to build dump_sym binary as well. Or the
step fails. Building microdump_stalkwalker caused the step to run, but not
having dump_sym causes it to fail.

[wychen, 2017-03-09 04:15:16]

On 2017/03/08 21:25:15, mikecase wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/2734423002/ by mailto:mikecase@chromium.org.
> 
> The reason for reverting is: So, needed to build dump_sym binary as well. Or
the
> step fails. Building microdump_stalkwalker caused the step to run, but not
> having dump_sym causes it to fail.

Reverting this doesn't seem to bring the bots back.

First failure:
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...

First build after the revert (still fail):
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...

[mikecase (-- gone --), 2017-03-09 04:44:14]

On 2017/03/09 at 04:15:16, wychen wrote:
> On 2017/03/08 21:25:15, mikecase wrote:
> > A revert of this CL (patchset #1 id:1) has been created in
> > https://codereview.chromium.org/2734423002/ by mailto:mikecase@chromium.org.
> > 
> > The reason for reverting is: So, needed to build dump_sym binary as well. Or
the
> > step fails. Building microdump_stalkwalker caused the step to run, but not
> > having dump_sym causes it to fail.
> 
> Reverting this doesn't seem to bring the bots back.
> 
> First failure:
>
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...
> 
> First build after the revert (still fail):
>
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...

ugh, I guess they don't clean their build directories between runs. I quick work
on a fix for this. Know a good solution

[mikecase (-- gone --), 2017-03-09 04:55:00]

On 2017/03/09 at 04:44:14, mikecase wrote:
> On 2017/03/09 at 04:15:16, wychen wrote:
> > On 2017/03/08 21:25:15, mikecase wrote:
> > > A revert of this CL (patchset #1 id:1) has been created in
> > > https://codereview.chromium.org/2734423002/ by
mailto:mikecase@chromium.org.
> > > 
> > > The reason for reverting is: So, needed to build dump_sym binary as well.
Or the
> > > step fails. Building microdump_stalkwalker caused the step to run, but not
> > > having dump_sym causes it to fail.
> > 
> > Reverting this doesn't seem to bring the bots back.
> > 
> > First failure:
> >
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...
> > 
> > First build after the revert (still fail):
> >
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...
> 
> ugh, I guess they don't clean their build directories between runs. I quick
work on a fix for this. Know a good solution

Landing a fix that will actually work here.

https://chromium-review.googlesource.com/c/451961/

[mikecase (-- gone --), 2017-03-09 06:37:23]

On 2017/03/09 at 04:55:00, mikecase wrote:
> On 2017/03/09 at 04:44:14, mikecase wrote:
> > On 2017/03/09 at 04:15:16, wychen wrote:
> > > On 2017/03/08 21:25:15, mikecase wrote:
> > > > A revert of this CL (patchset #1 id:1) has been created in
> > > > https://codereview.chromium.org/2734423002/ by
mailto:mikecase@chromium.org.
> > > > 
> > > > The reason for reverting is: So, needed to build dump_sym binary as
well. Or the
> > > > step fails. Building microdump_stalkwalker caused the step to run, but
not
> > > > having dump_sym causes it to fail.
> > > 
> > > Reverting this doesn't seem to bring the bots back.
> > > 
> > > First failure:
> > >
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...
> > > 
> > > First build after the revert (still fail):
> > >
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20We...
> > 
> > ugh, I guess they don't clean their build directories between runs. I quick
work on a fix for this. Know a good solution
> 
> Landing a fix that will actually work here.
> 
> https://chromium-review.googlesource.com/c/451961/

Bot is green. Should be fixed now