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,
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?
-why simutaneously run 2 test_shell ? for efficiency?
-while I'm
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
Okay, I think I've figured this out and it's a relatively undocumented
aspect of our win builds (from what I can tell).
The third_party/cygwin install we have has a modified version of
cygwin1.dll , which has been patched to tell cygwin the root is
third_party/cygwin rather than /. In order for
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
That's really weird, as I posted, between the two same layout-tests, one
succeeded on XP of my notebook, one failed on XP of my PC.
I totally agree with you, I think that must be something wrong about
ENVIROMENT, such as PATH.
FYI:
my PATH=D:\Program Files\Perl\bin;D:\Program
Well,new headway is I found it's really a weird bug. I copies the same source
from my pc to my notebook(both are Windows XP), and run layouttest.
The one on pc is still with the cygwin errors I've posted, but the notebook's
succeeded without any cygwin error.
I cann't explain that, could
I wasn't either, but a simple search provided this:
:: Set CYGWIN variable to 'nontsec'. That makes sure that permissions
:: on your windows machine are not updated as a side effect of cygwin::
operations.SET CYGWIN=nontsec
well, where to set it? in the run_webkit_tests.bat?
Well , I reviewed my layout-tests' output again, and found some errors like:
090629 14:28:30 __init__.py:1032 ERROR
LayoutTests/http/tests/xmlhttprequest/xml-encoding.html failed:
Text diff mismatch
Simplified text diff mismatch
/cygdrive/e/mychromesrc/src/third_party/cygwin/bin/wdiff:
In http://dev.chromium.org/developers/testing/webkit-layout-tests, it's wrote:
Tests marked as SKIP in
webkit/tools/layout_tests/test_lists/{mac,win}/tests_fixable.txt or
tests_ignored.txt won't be run at all, generally because they cause some
intractable tool error. To force one of them to
I reviewed my layout-tests' output, and found some errors like:
090629 14:28:30 __init__.py:1032 ERROR
LayoutTests/http/tests/xmlhttprequest/xml-encoding.html failed:
Text diff mismatch
Simplified text diff mismatch
/cygdrive/e/mychromesrc/src/third_party/cygwin/bin/wdiff: /tmp/t101c.0: No
I have ran layouttests on Windows XP, and got a result as:
Expected to fail, but passed (5):
LayoutTests/css2.1/t0805-c5519-brdr-r-01-e.html
LayoutTests/css2.1/t0905-c5525-fltblck-00-d-ag.html
LayoutTests/css2.1/t0905-c5525-flthw-00-c-g.html
LayoutTests/css2.1/t0905-c5526-flthw-00-c-g.html
hi,Evan
You can comment it out and just run gclient sync again. Not sure
why you'd want to pass the --revision flag.
I just wanna use one fixed revision, don't wanna update it everyday. Take that
into consideration, that's easy to fix problems.
Some data used by tests is not in the public
hi, pawel.
It is a bit worrying to me to read most of the tests fail. Do you
encounter more failures?
Yes, about 40% of my chrome's tests(I mean the .exe of tests) fail. And my
revision is r17306. I am wondering why, -_-!
--~--~-~--~~~---~--~~
Chromium Developers
I get a new question here:
I've checked most of chrome's tests, and haven't find a RUN_ALL_TEST() which I
think is necessary for GTest.
simply, the printing_unittests project.
why?
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
I'm trying to run chrome's tests, but find lots of failures up there.
I wanna ask:
1. most of tests fail like below, why?
[--] Global test environment tear-down
[==] 42 tests from 8 test cases ran. (3984 ms total)
[ PASSED ] 41 tests.
[ FAILED ] 1 test, listed below:
[ FAILED
16 matches
Mail list logo
