[chromium] TestWebKitAPI WTF.StringHasher_addCharacters is broken on Chromium Android. [ RUN ] WTF.StringHasher_addCharacters ../../third_party/WebKit/Tools/TestWebKitAPI/Tests/WTF/StringHasher.cpp:173: Failure Value of: hasher.hash() Actual: 452317957 Expected: testBHash5 Which is: 2032145993 [ RUN ] WTF.StringHasher_addCharactersAssumingAligned ../../third_party/WebKit/Tools/TestWebKitAPI/Tests/WTF/StringHasher.cpp:328: Failure Value of: hasher.hash() Actual: 452317957 Expected: testBHash5 Which is: 2032145993 [ FAILED ] WTF.StringHasher_addCharactersAssumingAligned
Created attachment 191197 [details] Patch
Are just the two tests failing? I'd just rename the tests to MAYBE_xxx and use an ifdef to rename MAYBE_xxx to either xxx or DISABLED_xxx
Oh we can use the familiar DISABLED_ prefix here... Sounds much better, I'll update the patch.
Created attachment 191204 [details] Patch
Updated the patch. (I guess this one can probably go without review-- let me just make sure it doesn't break)
CC-ing the original patch author too
Comment on attachment 191204 [details] Patch ok
Committed r144619: <http://trac.webkit.org/changeset/144619>
Very interesting. The fact that you get the wrong hash here on Android probably indicates a real problem. Someone should investigate what’s going on!
It’s bizarre that the code now references this bug. Instead, someone should file a bug about the hash values being incorrect and investigate why. And that’s the bug that the disabled test should point to.
Committed r145412: <http://trac.webkit.org/changeset/145412>