GitLab

The tests use EXPECT_EQ with a constant variable equal to false,
that tricks GCC 4.7+ into beliving the variable should be compatible to null
pointers in some internal macro. This CL workarounds that by
using EXPECT_TRUE(a == b) instead.

BUG=https://code.google.com/p/googletest/issues/detail?id=458
TBR=mek
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@271136 0039d316-1c4b-4281-b951-d872f2087c98