Bug 94562 landed without enabling the CString test for Chromium due to some failures on the EWS. I tried to reproduce the failures but couldn't, which matches Benjamin's experience. I did find a build breakage though related to the #include chain (not sure why no other platform complained). Let's fix Chromium and add this test!
The other String tests were also skipped on Chromium, let's enable everything if possible.
Created attachment 160284 [details] Proposed change: enable CString on Chromium and fix the debug build.
Comment on attachment 160284 [details] Proposed change: enable CString on Chromium and fix the debug build. OK, let's do it.
Created attachment 160294 [details] Better proposed change: enable all the Strings unit tests \o/
Comment on attachment 160294 [details] Better proposed change: enable all the Strings unit tests \o/ Thanks a lot for finding the problem.
Comment on attachment 160294 [details] Better proposed change: enable all the Strings unit tests \o/ Looks like r126509 got in the way :(
Created attachment 160302 [details] Patch for the EWS / landing.
Comment on attachment 160302 [details] Patch for the EWS / landing. Clearing flags on attachment: 160302 Committed r126530: <http://trac.webkit.org/changeset/126530>
All reviewed patches have been landed. Closing bug.