Disable flaky tests on Mac: PlatformChannelPairPosixTest.SendReceiveFDs and PipeCount/MultiprocessM…

Disable flaky tests on Mac: PlatformChannelPairPosixTest.SendReceiveFDs and PipeCount/MultiprocessMessagePipeTestWithPipeCount.PlatformHandlePassing/2

TBR=viettrungluu@chromium.org
BUG=488260, 488258
Committed: https://crrev.com/7a32c53b876983c4c33ebb570ffc7d41ef36e974
Cr-Commit-Position: refs/heads/master@{#330013}

[jam, 2015-05-14 22:44:56]

jam@chromium.org changed reviewers:
+ rockot@chromium.org

[jam, 2015-05-14 22:44:56]

Ken: how do we ensure that this doesn't get undisabled in next roll? we have to
also make the same change in the mojo repo? it seems unfortunate that tests fail
in the chromium repo and we have to disable them twice.

[jam, 2015-05-14 22:45:00]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-05-14 22:46:25]

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

[Ken Rockot(use gerrit already), 2015-05-14 22:52:52]

On 2015/05/14 22:46:25, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-cq-status.appspot.com/patch-status/1126293008/1

Hmm. Is there any reason why we shouldn't just stop running EDK unit tests on
chromium bots? Do we really run unit test suites for other third-party
dependencies?

[commit-bot: I haz the power, 2015-05-14 23:04:40]

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

[commit-bot: I haz the power, 2015-05-14 23:04:41]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[jam, 2015-05-15 00:32:28]

On 2015/05/14 22:52:52, Ken Rockot wrote:
> On 2015/05/14 22:46:25, I haz the power (commit-bot) wrote:
> > CQ is trying da patch. Follow status at
> >  https://chromium-cq-status.appspot.com/patch-status/1126293008/1
> 
> Hmm. Is there any reason why we shouldn't just stop running EDK unit tests on
> chromium bots? Do we really run unit test suites for other third-party
> dependencies?

The reason given to me when I asked is that the mojo waterfall doesn't have
mac/win bots. I still think it'd be better if these tests ran on the mojo tree,
so that they are run with each change and breakages are caught there, instead of
at rolltime into chromium.

[jam, 2015-05-15 01:11:16]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-05-15 01:11:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1126293008/20001

[commit-bot: I haz the power, 2015-05-15 01:30:35]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-05-15 01:31:40]

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