Bug 112661 - Tools/Scripts/build-dumprendertree mock command test is flakey
Summary: Tools/Scripts/build-dumprendertree mock command test is flakey
Status: RESOLVED DUPLICATE of bug 105951
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-18 22:45 PDT by Simon Fraser (smfr)
Modified: 2013-03-19 12:28 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2013-03-18 22:45:14 PDT
This webkitpy test is flakey:

http://build.webkit.org/builders/Apple%20Lion%20Release%20WK1%20%28Tests%29/builds/10549/steps/webkitpy-test/logs/stdio

[1089/1645] webkitpy.layout_tests.port.win_unittest.WinPortTest.test_build_driver failed:
  Traceback (most recent call last):
    File "/Volumes/Data/slave/lion-release-tests-wk1/build/Tools/Scripts/webkitpy/layout_tests/port/port_testcase.py", line 557, in test_build_driver
      self.assertTrue(output.assert_outputs(self, port._build_driver, expected_logs=expected_logs))
    File "/Volumes/Data/slave/lion-release-tests-wk1/build/Tools/Scripts/webkitpy/common/system/outputcapture.py", line 105, in assert_outputs
      testassert(logs_string, expected_logs)
  AssertionError: "MOCK run_command: ['Tools/Scripts/build-dumprendertree', '--release'], cwd=/moc [truncated]... != "MOCK run_command: ['Tools/Scripts/build-dumprendertree', '--release'], cwd=/moc [truncated]...
    MOCK run_command: ['Tools/Scripts/build-dumprendertree', '--release'], cwd=/mock-checkout, env={'LC_ALL': 'C', 'MOCK_ENVIRON_COPY': '1'}
  - [123456789ABCDEF0] Run adb command: ['shell', 'am', 'force-stop', 'org.chromium.native_test']
  - [123456789ABCDEF0] Run adb result: 
    Output of ['Tools/Scripts/build-dumprendertree', '--release']:
    MOCK output of child process
Comment 1 Dirk Pranke 2013-03-19 12:28:46 PDT
yeah, this is a known flaky test. Unfortunately, it's hard to figure out why it's flaky, and at least once when I  tried disabling it, it just made another test start failing.

In the past it hasn't been flaky enough to really be a problem, but if something has changed, that'd be good to know.

*** This bug has been marked as a duplicate of bug 105951 ***