110992 2013-02-27 10:22:04 -0800 [Chromium] RenderTableCellDeathTest unit test fails on mac 2013-02-28 06:36:50 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 schenney webkit-unassigned jchaffraix ojan oldest_to_newest 843212 0 schenney 2013-02-27 10:22:04 -0800 http://build.webkit.org/builders/Chromium%20Mac%20Release%20%28Tests%29/builds/34725/steps/webkit-unit-tests/logs/stdio [==========] Running 494 tests from 60 test cases. [----------] Global test environment set-up. [----------] 4 tests from RenderTableCellDeathTest [ RUN ] RenderTableCellDeathTest.CanSetColumn [ OK ] RenderTableCellDeathTest.CanSetColumn (28 ms) [ RUN ] RenderTableCellDeathTest.CanSetColumnToMaxColumnIndex [ OK ] RenderTableCellDeathTest.CanSetColumnToMaxColumnIndex (0 ms) [ RUN ] RenderTableCellDeathTest.CrashIfColumnOverflowOnSetting [WARNING] ../../Source/WebKit/chromium/testing/gtest/src/gtest-death-test.cc:823:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test detected 7 threads. 843396 1 schenney 2013-02-27 12:45:47 -0800 Committed r144227: <http://trac.webkit.org/changeset/144227> Disabled the test for now. 844029 2 schenney 2013-02-28 06:36:14 -0800 Committed r144303: <http://trac.webkit.org/changeset/144303> 844030 3 schenney 2013-02-28 06:36:50 -0800 The problem went away even with this test running, so it seems this test was not the issue after all.