Checking autoinstalled packages ...
Checking imports ...
Finding the individual test methods ...
Running the tests ...
[101/1258] webkitpy.common.prettypatch_unittest.PrettyPatchTest.test_pretty_diff_encodings erred:
Traceback (most recent call last):
File "E:\b\chromium-win-release-tests\build\Tools\Scripts\webkitpy\common\prettypatch_unittest.py", line 73, in test_pretty_diff_encodings
pretty = pretty_patch.pretty_diff(self._diff_with_multiple_encodings)
File "E:\b\chromium-win-release-tests\build\Tools\Scripts\webkitpy\common\prettypatch.py", line 67, in pretty_diff
return self._executive.run_command(args, input=diff, decode_output=False)
File "E:\b\chromium-win-release-tests\build\Tools\Scripts\webkitpy\common\system\executive.py", line 423, in run_command
(error_handler or self.default_error_handler)(script_error)
File "E:\b\chromium-win-release-tests\build\Tools\Scripts\webkitpy\common\system\executive.py", line 340, in default_error_handler
ScriptError: Failed to run "['ruby', '-I', 'E:\\b\\chromium-win-release-tests\\build\\Websites\\bugs.webkit.org\\PrettyPatch'..." exit_code: 1
[874/1258] webkitpy.layout_tests.run_webkit_tests_integrationtest.MainTest.test_verbose_in_child_processes passed
Okay, so it is unfortunate that ScriptError is limiting the output here, but I reproduced this locally on Windows and PrettyPatch is actually failing (i.e., this is a real failure, not a problem w/ test-webkitpy or anything like that); it looks like some combination of the utf-8 encoding and line-ending conversion doesn't work.
I'm going to disable the test on win32 for now until we can actually fix the issue.
Created attachment 157090 [details]
Committed r124973: <http://trac.webkit.org/changeset/124973>
sigh .. didn't mean to close the bug. Test disabled in http://trac.webkit.org/changeset/124973 . Note that the patch I uploaded was missing an 'import sys', and I fixed that prior to landing.
reassigning owner to default, since I'm not dying to fix this myself ;).
I've just verified (because it was failing also in our WK2 gtk bot) that the problem here is the ruby version.
Our bot was running ruby 1.9.1 and we were able to get rid of the bug by downgrading it to 1.8.7.
I won't change the title of the bug until Dirk could verify that the problem in chromium win is the same (I'd bet it's)