[MemSheriff] Disable two tests which are flaky by design.

[MemSheriff] Disable two tests which are flaky by design.

Previously only disabled on Win.

BUG=396393, 396386
TBR=jamesr@chromium.org
NOTRY=true

Committed: https://crrev.com/1d4c7f2b5dfe47e6fd8ed25068e126ec8584b91c
Cr-Commit-Position: refs/heads/master@{#313086}

[earthdok, 2015-01-26 17:35:27]

earthdok@chromium.org changed reviewers:
+ jamesr@chromium.org
- viettrungluu@chromium.org

[earthdok, 2015-01-26 17:36:03]

The CQ bit was checked by earthdok@chromium.org

[commit-bot: I haz the power, 2015-01-26 17:36:37]

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

[commit-bot: I haz the power, 2015-01-26 17:39:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-26 17:42:38]

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

[jam, 2015-01-26 17:49:06]

these source files are copied from the mojo (github) repo. so they'll need to be
disabled there, or else in the next code sync the test disabling will be lost.

we should also stop running mojo tests in third_party on the chromium waterfall.
they're already run in mojo's waterfall.

[earthdok, 2015-01-26 17:57:44]

On 2015/01/26 17:49:06, jam wrote:
> these source files are copied from the mojo (github) repo. so they'll need to
be
> disabled there, or else in the next code sync the test disabling will be lost.
Whoops. Viet-Trung, could you please do that?

> we should also stop running mojo tests in third_party on the chromium
waterfall.
> they're already run in mojo's waterfall.
we may want to keep them running on the MSan bot until mojo folks set up their
own MSan bot

[jam, 2015-01-26 18:00:43]

On 2015/01/26 17:57:44, earthdok wrote:
> On 2015/01/26 17:49:06, jam wrote:
> > these source files are copied from the mojo (github) repo. so they'll need
to
> be
> > disabled there, or else in the next code sync the test disabling will be
lost.
> Whoops. Viet-Trung, could you please do that?
> 
> > we should also stop running mojo tests in third_party on the chromium
> waterfall.
> > they're already run in mojo's waterfall.
> we may want to keep them running on the MSan bot until mojo folks set up their
> own MSan bot

we will run into the same issue as well though: the bot will turn red and the
fix will be in another repo, one which almost all chromium devs don't have
access to.

if we really care about running them under msan, those bots should be setup on
the mojo waterfall (they have asan there already btw)

[earthdok, 2015-01-26 18:09:54]

On 2015/01/26 18:00:43, jam wrote:
> we will run into the same issue as well though: the bot will turn red and the
> fix will be in another repo, one which almost all chromium devs don't have
> access to.
> 
> if we really care about running them under msan, those bots should be setup on
> the mojo waterfall (they have asan there already btw)

bug filed https://code.google.com/p/chromium/issues/detail?id=452090
if anyone wants to take on adding an MSan bot for mojo, I'll be happy to help