If you try to run test-webkitpy from a directory one level up from OpenSource, it fails. It appears we are hard coding a directory path in the script to find the supporting files.
This is what I saw when I tried to run it outside of a webkit checkout: webkitpy.test.main: INFO Excluding: webkitpy.common.checkout.scm_unittest (use --all to include) The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit ...............................................................................................................................................................................The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit .The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit .The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit .The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit .The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit .The current directory (/Projects) is not a WebKit checkout, using /Projects/WebKit ..............................root: INFO this should be logged ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ ---------------------------------------------------------------------- Ran 974 tests in 18.089s OK It passed though... Could you explain what failure you see?
I suspect it may be getting confused by .svn files in the directory you're running it from? I know dpranke did some hacking to help it find the WebKit checkout when run inside chromium. That may be related to (or may have broken) your specific case.
(In reply to comment #2) > I suspect it may be getting confused by .svn files in the directory you're running it from? I know dpranke did some hacking to help it find the WebKit checkout when run inside chromium. That may be related to (or may have broken) your specific case. I think Eric is correct about the diagnosis but confused about the blame. I didn't do anything to make this worse AFAIK, and it's been broken for quite a while. See bug 56888 which is likely the same problem in a different direction.
bug 56888 looks to be culprit, marking as dupe. *** This bug has been marked as a duplicate of bug 56888 ***