Something underneath us is logging the above to stdout sometimes. Currently I only see it on Mavericks Release WK1, but have no reason to thing that’s a stable thing. I filed <rdar://problem/15450692> about the logging, but we need to do something about the failing test. I don’t think it’s possible to check in expected results that are that specific, so I’m going to mark it expected-fail in that configuration and then we’ll notice if it changes.
(In reply to comment #0) > Something underneath us is logging the above to stdout sometimes. Currently I only see it on Mavericks Release WK1, but have no reason to thing that’s a stable thing. > > I filed <rdar://problem/15450692> about the logging, but we need to do something about the failing test. I don’t think it’s possible to check in expected results that are that specific, so I’m going to mark it expected-fail in that configuration and then we’ll notice if it changes. Nope, have to mark it flaky, because the logging does not reproduce on all machines.
Marked flaky in http://trac.webkit.org/changeset/159135. Jer or Eric, if there’s something better we can do about this, please do!
We added support to run-webkit-tests to strip out this kind of logging in bug #125357. We can probably re-enable this test.
Committed r173488: <http://trac.webkit.org/changeset/173488>
The test is still flaky, which is tracked as bug 137505.
<rdar://problem/19521557>