Revert of Create symlink to adb in home dir right before device setup.

Revert of Create symlink to adb in home dir right before device setup. (patchset #3 id:40001 of https://codereview.chromium.org/1818083003/ )

Reason for revert:
Fails on WebRTC bots, example:
https://build.chromium.org/p/client.webrtc/builders/Android32%20Tests%20%28L%20Nexus5%29%28dbg%29/builds/6015

See previous CL message for details. Since those bots turning purple blocks our CQ, I'm reverting this.

Original issue's description:
> Create symlink to adb in home dir right before device setup.
> 
> Depends on https://codereview.chromium.org/1811933007/
> 
> BUG=565452
> 
> Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299412

TBR=jbudorick@chromium.org,bpastene@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=565452
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299419

[kjellander_chromium, 2016-03-22 10:21:26]

Created Revert of Create symlink to adb in home dir right before device setup.

[commit-bot: I haz the power, 2016-03-22 10:21:35]

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

[commit-bot: I haz the power, 2016-03-22 10:22:40]

Description was changed from

==========
Revert of Create symlink to adb in home dir right before device setup. (patchset
#3 id:40001 of https://codereview.chromium.org/1818083003/ )

Reason for revert:
Fails on WebRTC bots, example:
https://build.chromium.org/p/client.webrtc/builders/Android32%20Tests%20%28L%...

See previous CL message for details. Since those bots turning purple blocks our
CQ, I'm reverting this.

Original issue's description:
> Create symlink to adb in home dir right before device setup.
> 
> Depends on https://codereview.chromium.org/1811933007/
> 
> BUG=565452
> 
> Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299412

TBR=jbudorick@chromium.org,bpastene@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=565452
==========

to

==========
Revert of Create symlink to adb in home dir right before device setup. (patchset
#3 id:40001 of https://codereview.chromium.org/1818083003/ )

Reason for revert:
Fails on WebRTC bots, example:
https://build.chromium.org/p/client.webrtc/builders/Android32%20Tests%20%28L%...

See previous CL message for details. Since those bots turning purple blocks our
CQ, I'm reverting this.

Original issue's description:
> Create symlink to adb in home dir right before device setup.
> 
> Depends on https://codereview.chromium.org/1811933007/
> 
> BUG=565452
> 
> Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299412

TBR=jbudorick@chromium.org,bpastene@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=565452

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299419
==========

[commit-bot: I haz the power, 2016-03-22 10:22:42]

Committed patchset #1 (id:1) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=299419

[bpastene, 2016-03-22 16:44:53]

On 2016/03/22 10:22:42, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1) as
> http://src.chromium.org/viewvc/chrome?view=rev&revision=299419

lgtm

This problem was solved with
https://chromium.googlesource.com/chromium/src/+/a516b28437b3f5f483b2dc9e7f17...

Any chance we can get chromium's pin in webRTC bumped up to that version or
later?

[kjellander_chromium, 2016-03-22 17:01:36]

On 2016/03/22 16:44:53, bpastene wrote:
> On 2016/03/22 10:22:42, commit-bot: I haz the power wrote:
> > Committed patchset #1 (id:1) as
> > http://src.chromium.org/viewvc/chrome?view=rev&revision=299419
> 
> lgtm
> 
> This problem was solved with
>
https://chromium.googlesource.com/chromium/src/+/a516b28437b3f5f483b2dc9e7f17...
> 
> Any chance we can get chromium's pin in webRTC bumped up to that version or
> later?

Oh, then I'm sorry about the revert. Our rolling has been blocked on a GYP issue
related to mojo which I haven't been able to resolve yet (perf season etc). I'll
try to find time today and see if we can resolve it.

[chromium-reviews, 2016-03-24 05:25:45]

Our roll was fixed yesterday. Forgot to tell you. Feel free to reland.

-- sent from my Nexus 6
On Mar 22, 2016 18:01, <kjellander@chromium.org> wrote:

> On 2016/03/22 16:44:53, bpastene wrote:
> > On 2016/03/22 10:22:42, commit-bot: I haz the power wrote:
> > > Committed patchset #1 (id:1) as
> > > http://src.chromium.org/viewvc/chrome?view=rev&revision=299419
> >
> > lgtm
> >
> > This problem was solved with
> >
>
>
https://chromium.googlesource.com/chromium/src/+/a516b28437b3f5f483b2dc9e7f17...
> >
> > Any chance we can get chromium's pin in webRTC bumped up to that version
> or
> > later?
>
> Oh, then I'm sorry about the revert. Our rolling has been blocked on a GYP
> issue
> related to mojo which I haven't been able to resolve yet (perf season
> etc). I'll
> try to find time today and see if we can resolve it.
>
> https://codereview.chromium.org/1821973002/
>

-- 
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.

[bpastene, 2016-03-24 16:23:58]

On 2016/03/24 05:25:45, chromium-reviews wrote:
> Our roll was fixed yesterday. Forgot to tell you. Feel free to reland.

Cool, I'll try relanding today and will monitor the webrtc bots.