Actually, the data is messed up. It's the windows bots. The path isn't being
made relative properly. It's getting full windows paths in the results.json
file. We'll need to do a cleanup pass. Dirk, you want to do that, or should
I?

On Thu, Jan 14, 2010 at 10:40 AM, Ojan Vafai <o...@google.com> wrote:

> I think the data for the dashboard is fine. There's just some dashboard
> logic that needs updating. Will get on that ASAP.
>
> On Wed, Jan 13, 2010 at 6:47 PM, Dirk Pranke <dpra...@chromium.org> wrote:
>
>> Hi all,
>>
>> If you never run layout tests or modify test_expectations.txt, you can
>> stop reading.
>>
>> As part of the process to upstream our layout test infrastructure, I
>> have just checked in a change that changes our test infrastructure to
>> conform to WebKit's in how we specify test names.
>>
>> Specifically, instead of saying "LayoutTests/fast/html/foo.html", you
>> now just say "fast/html/foo.html". This affects specifying tests on
>> the command line to run_webkit_tests, and also specifying test names
>> in test_expectations.txt .
>>
>> In the near future, we will also be moving all of the baselines from
>>
>> src/webkit/data/layout_tests/platform/chromium-{mac,win,linux}/LayoutTests/*
>> to platform/chromium-{mac,win,linux}/*, again to match WebKit's
>> structure.
>>
>> Two notes:
>>
>> 1) I believe the rebaselining tool is working correctly, but I'm not
>> 100% sure. If you have any problems, let me know.
>>
>> 2) I may have just corrupted the data sets used by the flakiness
>> dashboard. I will be checking this with Ojan and (hopefully) fixing it
>> later this evening if I did.
>>
>> Any questions or problems to me. Thanks!
>>
>> -- Dirk
>>
>> --
>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>> View archives, change email options, or unsubscribe:
>>    http://groups.google.com/group/chromium-dev
>>
>
>
-- 
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev

Reply via email to