| Summary: | chromium_android_unittest fails on Apple Windows port | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Roger Fong <roger_fong> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | peter, roger_fong |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
A bug that I think is related: https://bugs.webkit.org/show_bug.cgi?id=96393 patch to skip assert: http://trac.webkit.org/changeset/130309 Resolving as WontFix given that Chromium moved to Blink. |
[439/1585] webkitpy.layout_tests.port.chromium_android_unittest.ChromiumAndroidDriverTest.test_command_from_driver_input failed: Traceback (most recent call last): File "/home/buildbot/slave/win-release-tests/build/Tools/Scripts/webkitpy/layout_tests/port/chromium_android_unittest.py", line 247, in test_command_from_driver_input self.assertEquals(self.driver._command_from_driver_input(driver_input), expected_command) AssertionError: "C:\\cygwin\\mock-checkout\\LayoutTests\\foo\\bar\\test.html'--pixel-test'checksum\n" != "/data/local/tmp/third_party/WebKit/LayoutTests/foo/bar/test.html'--pixel-test'checksum\n" I don't know when it started failing. No regression ranges for the py tests unfortunately. Do we even care about this test on Windows? Doesn't seem particularly relevant. I'm just adding a sys.platform check for now to skip the failing assertion.