hi, dave.
I think you're right. I ran the layout-test, and got the same result as
yours. I mean, I also got a lot of ERRORs as you described. And I think
most of these ERRORs are expected.
To your situation, the 9 unexpected + sum of expected = the sum of
ERRORs you get in your DOS.
2009/7/9
Ok, let me make question simple.
I get some ERRORs on my DOS while running layout-test, such as :
090706 15:37:19 __init__.py:1032 ERROR
LayoutTests/fast/backgrounds/svg-as-mask.html failed:
Text diff mismatch
Image mismatch
These ERRORs are made of two kinds: expected and unexpected,
2009/7/6 David Jones ds...@163.com
I have worked on webkit ,though I didn't know much about wekkit's
layout-test. I'm curious about chrome's layout-test.
-do you take webkit's layout-test into chrome with any changes? I don't
think so, so what're these changes?
It depends a little on the
It means those two tests failed to produce the expected results. When done,
the summary page should open with a list of any tests that didn't result in
the expected way, with links to see the expected, actual and difference in
values.
really? While runing layout-test, I always get a lot of
See the expectations file, it lists the ones that are known to fail on a
given platform. This is how we easily track new failures.
TVL
2009/7/6 David Jones ds...@163.com
It means those two tests failed to produce the expected results. When
done, the summary page should open with a list of
See the expectations file, it lists the ones that are known to fail on a
given platform. This is how we easily track new failures.
Most of the ERRORs I get such as :
090706 15:37:19 __init__.py:1032 ERROR
LayoutTests/fast/backgrounds/svg-as-mask.html failed:
Text diff mismatch
Image
