[chromium-dev] Re: some questions about chrome's layout-test
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, the unexpected ERRORs will be counted as the final number in : 090706 15:44:24 __init__.py:1032 INFO Exit status: 9 right?? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] some questions about chrome's layout-test
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 runing run_webkit_test.bat, my DOS always display ERROR as below: 090706 15:37:19 __init__.py:1032 ERROR LayoutTests/fast/backgrounds/svg-as-mask.html failed: Text diff mismatch Image mismatch 090706 15:37:20 __init__.py:1032 ERROR LayoutTests/fast/block/float/013.html failed: Text diff mismatch Image mismatch 090706 15:37:21 __init__.py:1032 ERROR LayoutTests/fast/block/float/nested-clearance.html failed: Text diff mismatch Image mismatch What does that mean? Which __init__.py does it use? I find a lot of __init__.py under chromium --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: some questions about chrome's layout-test
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 ERRORs. But at the end, I get a summary 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 LayoutTests/fast/encoding/invalid-UTF-8.html Expected to timeout, but passed (1): LayoutTests/http/tests/security/credentials-in-referer.html Regressions: Unexpected failures (8): LayoutTests/fast/css/css2-system-fonts.html = FAIL LayoutTests/fast/dom/anchor-toString.html = FAIL LayoutTests/fast/dom/java-applet-calls.html = FAIL LayoutTests/fast/dom/object-embed-plugin-scripting.html = FAIL LayoutTests/http/tests/security/cross-frame-access-protocol-explicit-domain.ht ml = FAIL LayoutTests/http/tests/security/cross-frame-access-protocol.html = FAIL LayoutTests/platform/win/fast/text/uniscribe-missing-glyph.html = FAIL LayoutTests/plugins/embed-attributes-setting.html = FAIL Regressions: Unexpected timeouts (1): LayoutTests/http/tests/security/originHeader/origin-header-for-https.html = TIMEOUT -- = Tests to be fixed for the current release (786): 88 test cases (11.2%) Passed 364 test cases (46.3%) Skipped 287 test cases (36.5%) Text diff mismatch 190 test cases (24.2%) Simplified text diff mismatch 160 test cases (20.4%) Image mismatch 10 test cases (1.3%) Test timed out 6 test cases (0.8%) Test shell crashed 2 test cases (0.3%) No expected image found = Tests we want to pass for the current release (8984): 8273 test cases (92.1%) Passed 364 test cases (4.1%) Skipped 299 test cases (3.3%) Text diff mismatch 200 test cases (2.2%) Simplified text diff mismatch 164 test cases (1.8%) Image mismatch 11 test cases (0.1%) Test timed out 6 test cases (0.1%) Test shell crashed 2 test cases (0.0%) No expected image found = Tests to be fixed for a future release (0): = All tests (10884): 8752 test cases (80.4%) Passed 2130 test cases (19.6%) Skipped 409 test cases (3.8%) Text diff mismatch 301 test cases (2.8%) Simplified text diff mismatch 183 test cases (1.7%) Image mismatch 12 test cases (0.1%) Test timed out 6 test cases (0.1%) Test shell crashed 2 test cases (0.0%) No expected image found 090706 15:44:24 __init__.py:1032 INFO Exit status: 9 090706 15:44:24 __init__.py:1032 INFO flushing stdout 090706 15:44:24 __init__.py:1032 INFO flushing stderr 090706 15:44:24 __init__.py:1032 INFO stopping http server 090706 15:44:24 __init__.py:1032 INFO Shutting down http server I think that means only 9 ERRORs should happen. Is that a contradiction? puzzled.. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cygwin dependence missing?
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 this to work correctly, you need to run third_party/cygwin/setup_mount.bat to stuff the right entries into the registry. We should probably change run_layout_tests to automatically run this script prior to running the regression (running it every time should be harmless). -- Dirk Do you mean my layout-test actually uses the cygwin under depot_tools, but not the third_party/cygwin? also, what does setup_mount.bat do? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: some questions about chrome's layout-test
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 mismatch are just an ERROR that is to be expected, so they are not included in the final summary, which means not included in the final regression errors: 090706 15:44:24 __init__.py:1032 INFO Exit status: 9 right? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cygwin dependence missing?
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 Files\Perl\site\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Program Files\Rational\common;D:\Program Files\Rational\ClearCase\bin;C:\Python24;C:\Python24\Scripts;D:\depot_tools; --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cygwin dependence missing?
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 anyone explain that? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cygwin dependence missing?
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? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: how to judge layouttests' running result?
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: /tmp/t101c.0: No such file or directory I think I missed something, right? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] tests_expectations.txt
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 be run, either rename that file
or specify the skipped test as the only one on the command line (see below).
But in my chromium source, I didn't find a tests_fixable.txt or
tests_ignored.txt, but a test_expectations.txt.
Is that a carelessness while writing WebKit Layout Tests??
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
[chromium-dev] cygwin dependence missing?
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 such file or directory I think I missed something about cygwin, right? How to make up? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] how to judge layouttests' running result?
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 LayoutTests/fast/encoding/invalid-UTF-8.html Expected to timeout, but passed (1): LayoutTests/http/tests/security/credentials-in-referer.html Regressions: Unexpected failures (8): LayoutTests/fast/css/css2-system-fonts.html = FAIL LayoutTests/fast/dom/anchor-toString.html = FAIL LayoutTests/fast/dom/java-applet-calls.html = FAIL LayoutTests/fast/dom/object-embed-plugin-scripting.html = FAIL LayoutTests/http/tests/security/cross-frame-access-protocol-explicit-domain.ht ml = FAIL LayoutTests/http/tests/security/cross-frame-access-protocol.html = FAIL LayoutTests/platform/win/fast/text/uniscribe-missing-glyph.html = FAIL LayoutTests/plugins/embed-attributes-setting.html = FAIL Regressions: Unexpected timeouts (1): LayoutTests/http/tests/security/originHeader/origin-header-for-https.html = TI MEOUT -- = Tests to be fixed for the current release (786): 86 test cases (10.9%) Passed 364 test cases (46.3%) Skipped 289 test cases (36.8%) Text diff mismatch 191 test cases (24.3%) Simplified text diff mismatch 160 test cases (20.4%) Image mismatch 11 test cases (1.4%) Test timed out 6 test cases (0.8%) Test shell crashed 2 test cases (0.3%) No expected image found = Tests we want to pass for the current release (8984): 8271 test cases (92.1%) Passed 364 test cases (4.1%) Skipped 301 test cases (3.4%) Text diff mismatch 201 test cases (2.2%) Simplified text diff mismatch 164 test cases (1.8%) Image mismatch 12 test cases (0.1%) Test timed out 6 test cases (0.1%) Test shell crashed 2 test cases (0.0%) No expected image found = Tests to be fixed for a future release (0): = All tests (10884): 8753 test cases (80.4%) Passed 2130 test cases (19.6%) Skipped 411 test cases (3.8%) Text diff mismatch 302 test cases (2.8%) Simplified text diff mismatch 183 test cases (1.7%) Image mismatch 13 test cases (0.1%) Test timed out 6 test cases (0.1%) Test shell crashed 2 test cases (0.0%) No expected image found I don't know what it tells, am I passed the layouttests? There's also a layouttests in webkit, what's the relation between chrome's layouttest and webkit's layouttest? I think webkit's layouttest only run on Leopard. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] [chromium-dev]RE: why some chrome's tests fail?
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 tree, as many (like performance tests) are attempting to test against real web sites and we can't republish their content. while, that must be a bug of chrome's test. I copied the url: file:///F:/chrometrunk/src/data/tab_switching/kannada.chakradeo.net/index.html from the url bar of chrome's tab_switching_test.exe, and chrome doesn't find that index.html. So I asked. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] why some chrome's tests fail?
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 mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] why some chrome's tests fail?
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: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] why some chrome's tests fail?
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 ] TextEliderTest.TestGeneralEliding 1 FAILED TEST YOU HAVE 1 DISABLED TEST 2.I want to test webkit with its layouttest, but find src/webkit/data/layout_tests/LayoutTests: None in .gclient. If I comment it out and execute gclient sync --rivision s...@ Will I get the layouttest? 3.I think I miss some test data in my src, but I did get a completed gclient sync which I'm very sure. For exmaple, in tab_switching_tests, I can't find src/data/ directory which is a part of testing url: file:///F:/chrometrunk/src/data/tab_switching/kannada.chakradeo.net/index.html --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
