I'm starting to hate mock tests. It's a bug. The fix is one line, but it might be delayed a bit while I figure out a better way to test this. Mihai's workaround should tide you over.
Sorry for the inconvenience, -- Dirk On Fri, Nov 19, 2010 at 7:47 AM, W. James MacLean <wjmacl...@chromium.org> wrote: > > I'm trying to generate baselines for a new test, using the command > WebKitTools/Scripts/new-run-webkit-tests --new-baseline <test> > I have previously done (successfully) > WebKitTools/Scripts/build-webkit > WebKitTools/Scripts/build-dumprendertree > When I try to run the new-run-webkit-tests, it tells me that it cannot find > DumpRenderTree. It was looking in > WebKitBuild/ > instead of > WebKitBuild/Release > where the executables actually were. After copying both DumpRenderTree and > ImageDiff up from the Release directory, I now get a failed test because > DumpRenderTree crashed, and the stack trace is full of messages like > DumpRenderTree[44776:903] Failed to activate fonts: blah ... blah ... > I am using the wrong work flow? Why is the build script putting executables > in one place wile new-run-webkit-tests is looking for them in another place? > James > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
