Fix the build from revert in r159372

EventNames -> EventTypeNames apparently.

TBR=ojan@chromium.org
BUG=306179

Review URL: https://codereview.chromium.org/26915002

git-svn-id: svn://svn.chromium.org/blink/trunk@159373 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Mark local failures in TestExpectations.

It's silly for everyone to see these failures locally when we
already have bugs on file documenting their existence.

I suspect these must pass on the bots, or we would have marked these as failing long ago.  They may both be clang=1 failures.

BUG=255714,231910

Review URL: https://codereview.chromium.org/26882004

git-svn-id: svn://svn.chromium.org/blink/trunk@159374 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add flaky tests.

TBR=pfeldman@chromium.org

Review URL: https://codereview.chromium.org/26896004

git-svn-id: svn://svn.chromium.org/blink/trunk@159375 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Assertions for RefCountedBase::m_deletionHasBegun should be ASSERT_WITH_SECURITY_IMPLICATION.

They are typical signals for use-after-free.

The main changes are:
 - Convert ASSERT(!m_deletionHasBegun) to ASSERT_WITH_SECURITY_IMPLICATION
   (!m_deletionHasBegun).
 - Move them out from CHECK_REF_COUNTED_LIFECYCLE blocks, and wrap them with
   SECURITY_ASSERT_ENABLED

CSSValue.cpp and StyleRule.cpp:
  RefCountedBase ends with "bool m_deletionHasBegun" in Release + ASAN
build. Bitfields in CSSValue and StyelRule can be merged with
m_deletionHasBegun, and their actual sizes can be smaller.

BUG=none
TEST=none; no behavior changes

Review URL: https://codereview.chromium.org/26279011

git-svn-id: svn://svn.chromium.org/blink/trunk@159377 bbb929c8-8fbe-4397-9dbb-9b2b20218538