This is the output that I'm currently getting from NRWT on Lion (there is a test landed without results):
compositing/tiling/crash-reparent-tiled-layer.html -> unexpected text diff mismatch
http/tests/appcache/origin-usage.html -> unexpected text diff mismatch
css2.1/t0602-c13-inheritance-00-e.html -> unexpected text diff mismatch
http/tests/cookies/simple-cookies-max-age.html -> unexpected text diff mismatch
canvas/philip/tests/2d.path.stroke.prune.arc.html -> unexpected text diff mismatch
fast/canvas/webgl/canvas-test.html -> unexpected text diff mismatch
Testing (38%): 10203 ran as expectedWriting new expected result "fast/exclusions/triangle-exclusion-expected.txt"
fast/exclusions/triangle-exclusion.html -> unexpected no expected result found
fast/files/create-blob-url-crash.html -> unexpected text diff mismatch
fast/text/complex-preferred-logical-widths.html -> unexpected text diff mismatch
fast/text/hyphenate-locale.html -> unexpected text diff mismatch
The line for "Writing new expected result" looks wrong.
By "looks wrong" I'm guessing you mean that there should've been a carriage return in between "expected" and "Writing"?
This is a known flaw in the way stuff gets logged to stderr in NRWT by default; messages in the worker processes interleave with the "progress meter" in the manager process.
We have not bothered to implement the "general" solution that would coordinate messages between processes; the hack we normally employ is to print a blank line before printing messages from the workers. Such a hack is a trivial fix.
this is actually a duplicate of 63793.
*** This bug has been marked as a duplicate of bug 63793 ***