Ah, I found it. My LOG(INFO)s weren't getting printed correctly, a two-hour red herring.
The problem was that DIR_SOURCE_ROOT was wrong for bundles, while it worked fine for the test executables. I guess this was the first use from w/in Chromium or TestShell. On Wed, Apr 22, 2009 at 9:33 AM, Mike Pinkerton <[email protected]> wrote: > The problem I'm seeing is that this is getting called before the > ChromePathProvider has been registered with the path service in the > browser, so it doesn't get any path. > > I'll keep digging as to why. > > On Tue, Apr 21, 2009 at 6:11 PM, Tony Chang <[email protected]> wrote: >> It tries to get it from PathService::Get(chrome::DIR_TEST_DATA). Is that >> variable set for mac? >> (see chrome/browser/automation/automation_provider.cc:2117) >> >> On Tue, Apr 21, 2009 at 2:49 PM, Mike Pinkerton <[email protected]> >> wrote: >>> >>> Anyone familiar with how URLRequestMockHTTPJob is supposed to locate >>> files? The UI tests just pass it a filename (no path, no nothing) and >>> expect it to be found. On Mac, at least, this just ends up passing >>> straight through so the FilePath looks like "/filename.html" which is >>> clearly isn't going to find the Debug directory. >>> >>> It's looking for things in chrome/test/data. How does this extra >>> mapping get done? Am I missing something obvious? >>> >>> -- >>> Mike Pinkerton >>> Mac Weenie >>> [email protected] >>> >>> >>> >> >> > > > > -- > Mike Pinkerton > Mac Weenie > [email protected] > -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
