summaryrefslogtreecommitdiffstats
path: root/net/socket
diff options
context:
space:
mode:
authoryfriedman@chromium.org <yfriedman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-20 23:12:37 +0000
committeryfriedman@chromium.org <yfriedman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-20 23:12:37 +0000
commit1ce036139aba74ac80a94100c315d56a4eabcae2 (patch)
treebc65e4311e04b7d6f1cfc97c695f830b6435f882 /net/socket
parent3060ce78db15f4a923d949ab5c1aaa5f75a1a066 (diff)
downloadchromium_src-1ce036139aba74ac80a94100c315d56a4eabcae2.zip
chromium_src-1ce036139aba74ac80a94100c315d56a4eabcae2.tar.gz
chromium_src-1ce036139aba74ac80a94100c315d56a4eabcae2.tar.bz2
Another fix in in_memory_url_index_unittest compilation for Android.
Due to oddities in STLPort, the gtest macros have some incompatibilities when outputting failure information for some iterators. Changing from ASSERT_NE to an equivalent ASSERT_TRUE avoid this auto-generated output. See also: http://codereview.chromium.org/9649006/ I looked into gtest a bit and tried define a PrintTo for some of these types but I wasn't able to fix it that way. BUG=117407 TEST= Review URL: http://codereview.chromium.org/9701062 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127825 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/socket')
0 files changed, 0 insertions, 0 deletions