Suppress a deadlock in TraceEventTestFixture.ThreadOnceBlocking

Suppress a deadlock in TraceEventTestFixture.ThreadOnceBlocking

BUG=397022
TBR=earthdok@chromium.org
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=285261

[Alexander Potapenko, 2014-07-24 07:54:34]

The CQ bit was checked by glider@chromium.org

[commit-bot: I haz the power, 2014-07-24 07:57:02]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/glider@chromium.org/411283003/1

[Alexander Potapenko, 2014-07-24 09:05:36]

On 2014/07/24 07:57:02, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-status.appspot.com/cq/glider@chromium.org/411283003/1

TBR

[commit-bot: I haz the power, 2014-07-24 14:43:31]

Change committed as 285261

[Derek Bruening, 2014-07-24 16:56:12]

I would suggest replacing the old tools/valgrind/tsan/suppressions.txt with a
pointer to this file, as I (along with other Memory Sheriffs I pinged) was not
aware that this base/debug/tsan_suppressions.cc file existed and that this was
how to suppress tsan errors.  The fact that there is no suppression info in the
error report on the bot implied that suppressions were just not supported.

[Alexander Potapenko, 2014-07-24 17:33:25]

On 2014/07/24 16:56:12, Derek Bruening wrote:
> I would suggest replacing the old tools/valgrind/tsan/suppressions.txt with a
> pointer to this file, as I (along with other Memory Sheriffs I pinged) was not
> aware that this base/debug/tsan_suppressions.cc file existed and that this was
> how to suppress tsan errors.  The fact that there is no suppression info in
the
> error report on the bot implied that suppressions were just not supported.

Will do. Note the suppressions are also mentioned in the TSan v2 documentation
on dev.chromium.org