RESOLVED WONTFIX 86262
[Chromium] check-webkit-style has opaque error output 
https://bugs.webkit.org/show_bug.cgi?id=86262
Summary [Chromium] check-webkit-style has opaque error output
Jeff Timanus
Reported 2012-05-11 15:34:59 PDT
The default Chromium check-out of webkit does not pull a complete repository. Attempting to run check-webkit-style in a Chromium checkout in cygwin on Windows produces the following output, which is not very clear: $ ../Tools/Scripts/check-webkit-style --verbose webkitpy.common.system.logutils: DEBUG Debug logging enabled. webkitpy.style.main: DEBUG Verbose logging enabled. webkitpy.style.main: DEBUG Changing to checkout root: /cygdrive/D/src/chromiu m_src/src/third_party/WebKit/Source Traceback (most recent call last): File "../Tools/Scripts/check-webkit-style", line 46, in <module> sys.exit(CheckWebKitStyle().main()) File "/cygdrive/D/src/chromium_src/src/third_party/WebKit/Tools/Scripts/webkit py/style/main.py", line 152, in main patch = host.scm().create_patch(options.git_commit, changed_files=changed_fi les) File "/cygdrive/D/src/chromium_src/src/third_party/WebKit/Tools/Scripts/webkit py/common/checkout/scm/svn.py", line 254, in create_patch decode_output=False) File "/cygdrive/D/src/chromium_src/src/third_party/WebKit/Tools/Scripts/webkit py/common/checkout/scm/scm.py", line 77, in run decode_output=decode_output) File "/cygdrive/D/src/chromium_src/src/third_party/WebKit/Tools/Scripts/webkit py/common/system/executive.py", line 420, in run_command close_fds=self._should_close_fds()) File "/cygdrive/D/src/chromium_src/src/third_party/WebKit/Tools/Scripts/webkit py/common/system/executive.py", line 476, in popen return subprocess.Popen(*args, **kwargs) File "/usr/lib/python2.6/subprocess.py", line 633, in __init__ errread, errwrite) File "/usr/lib/python2.6/subprocess.py", line 1139, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory
Attachments
Add attachment proposed patch, testcase, etc.
Stephen Chenney
Comment 1 2013-04-09 17:06:11 PDT
Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.
Note You need to log in before you can comment on or make changes to this bug.