New issue
Advanced search Search tips

Issue 855753 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"__main__.LaunchDesktopTest.testHelpfulErrorMessage_AbnormalExit" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 22 2018

Issue description

"__main__.LaunchDesktopTest.testHelpfulErrorMessage_AbnormalExit" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySgsSBUZsYWtlIj9fX21haW5fXy5MYXVuY2hEZXNrdG9wVGVzdC50ZXN0SGVscGZ1bEVycm9yTWVzc2FnZV9BYm5vcm1hbEV4aXQM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
 

Comment 1 by shend@chromium.org, Jun 25 2018

Failed because the test could not start Chrome:

======================================================================
FAIL: testHelpfulErrorMessage_AbnormalExit (__main__.LaunchDesktopTest)
If Chrome fails to start abnormally, we should provide a useful error
----------------------------------------------------------------------
Traceback (most recent call last):
  File "../../chrome/test/chromedriver/test/run_py_tests.py", line 2672, in testHelpfulErrorMessage_AbnormalExit
    self.assertIn('Chrome failed to start', e.message)
AssertionError: 'Chrome failed to start' not found in u'unknown error: Failed to create a Chrome process.\n  (Driver info: chromedriver=2.40.569471 (35945aaf6e3735c80ed1019a700b44501fd02d87),platform=Mac OS X 10.13.5 x86_64)'

A bit weird considering all the other tests passed and they could presumably start Chrome. 

Tests haven't run in a while for some reason: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=chromedriver_py_tests&tests=testHelpfulErrorMessage_AbnormalExit

Comment 2 by shend@chromium.org, Jun 25 2018

Owner: johnchen@chromium.org
Status: Assigned (was: Untriaged)
Hi johnchen@, can you please take a look at this? Thanks!
Cc: crouleau@chromium.org
Components: Tests>WebDriver
Status: Fixed (was: Assigned)
This test has been deleted by r569481.

Sign in to add a comment