Excluding some PhysicalSocketTest tests on memcheck.

Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True

Committed: https://crrev.com/2ce871548f7385cd273e5a97d6ca72b3af8a6229
Cr-Commit-Position: refs/heads/master@{#12914}

[Taylor Brandstetter, 2016-05-25 20:44:03]

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

[Taylor Brandstetter, 2016-05-25 20:44:15]

Description was changed from

==========
Excluding some PhysicalSocketTest tests on memcheck.
==========

to

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=true
==========

[Taylor Brandstetter, 2016-05-25 20:44:25]

Description was changed from

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=true
==========

to

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True
==========

[kjellander_webrtc, 2016-05-26 07:35:04]

Hmm, this seems to be exactly what's needed to fix failures like
https://build.chromium.org/p/client.webrtc/builders/Linux%20Memcheck/builds/6007

but I can't explain the other leaks reported by the trybot. I guess it must be
some difference in the machine's OS/libc? I guess that's possible since one is a
GCE VM and one is a Chrome infra VM. Both should be Trusty though.

lgtm either way since when I look at
https://build.chromium.org/p/tryserver.webrtc/builders/linux_memcheck I see only
failed runs in the history.

[kjellander_webrtc, 2016-05-26 08:03:55]

On 2016/05/26 07:35:04, kjellander (webrtc) wrote:
> Hmm, this seems to be exactly what's needed to fix failures like
>
https://build.chromium.org/p/client.webrtc/builders/Linux%20Memcheck/builds/6007
> 
> but I can't explain the other leaks reported by the trybot. I guess it must be
> some difference in the machine's OS/libc? I guess that's possible since one is
a
> GCE VM and one is a Chrome infra VM. Both should be Trusty though.
> 
> lgtm either way since when I look at
> https://build.chromium.org/p/tryserver.webrtc/builders/linux_memcheck I see
only
> failed runs in the history.

I created https://codereview.webrtc.org/2016613003 in order to fix that
suppression.

[kjellander_webrtc, 2016-05-26 10:58:48]

I'm committing this since the failures causes noise in the commit waterfall and
that https://codereview.webrtc.org/2016613003/ solves the trybot error we saw
here.

[kjellander_webrtc, 2016-05-26 10:58:52]

The CQ bit was checked by kjellander@webrtc.org

[commit-bot: I haz the power, 2016-05-26 10:58:57]

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

[commit-bot: I haz the power, 2016-05-26 11:03:49]

Description was changed from

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True
==========

to

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True
==========

[commit-bot: I haz the power, 2016-05-26 11:03:50]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-26 11:03:54]

Description was changed from

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True
==========

to

==========
Excluding some PhysicalSocketTest tests on memcheck.

NOTRY=True

Committed: https://crrev.com/2ce871548f7385cd273e5a97d6ca72b3af8a6229
Cr-Commit-Position: refs/heads/master@{#12914}
==========

[commit-bot: I haz the power, 2016-05-26 11:03:55]

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