New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Archived
Closed: Jun 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

Devserver should be skipped if check_health fails.

Project Member Reported by, Feb 10 2017

Issue description

daisy_skate CQ failed:

Debug log:

02/10 09:44:02.135 ERROR|        dev_server:0427| Devserver call failed: "", timeout: 2.0 seconds, Error: 

        500 Internal Server Error
        The server encountered an unexpected condition which prevented it from fulfilling the request.
        Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cherrypy/", line 656, in respond
    response.body = self.handler()
  File "/usr/lib/python2.7/dist-packages/cherrypy/lib/", line 188, in __call__
    self.body = self.oldhandler(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cherrypy/", line 34, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/usr/local/google/home/chromeos-test/chromiumos/src/platform/dev/", line 1510, in check_health
    apache_client_count = self._get_process_count('apache')
  File "/usr/local/google/home/chromeos-test/chromiumos/src/platform/dev/", line 1489, in _get_process_count
    'pgrep -fc "%s"' % process_cmd_pattern, shell=True))
  File "/usr/lib/python2.7/", line 566, in check_output
    process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/", line 1215, in _execute_child
    errpipe_read, errpipe_write = self.pipe_cloexec()
  File "/usr/lib/python2.7/", line 1167, in pipe_cloexec
    r, w = os.pipe()
OSError: [Errno 24] Too many open files


Comment 1 by, Feb 10 2017

Issue 690840 has been merged into this issue.

Comment 2 by, Feb 10 2017

Labels: Hotlist-Fixit
Summary: Devserver should be skipped if check_health fails. (was: daisy_skate CQ: Devserver call failed: "", timeout: 2.0 seconds)
Retooling this into a fixit bug.

Essentially if we hit an error when checking the health of the devserver, we should go on to the next one.

Comment 3 by, Jun 21 2017

Status: Started (was: Untriaged)

Comment 4 by, Jun 21 2017

hmm, actually we did do "when devserver health checking failed, go on to the next one", but the log doesn't clearly show that. Will fix this bug by adding more logs.

Another problem is this is actually a crash_devserver check fail, which won't be the real reason for a CQ failure.
Project Member

Comment 5 by, Jun 22 2017

The following revision refers to this bug:

commit b273f6fab2b1fc34b60f091151dd1984acbfeb46
Author: xixuan <>
Date: Thu Jun 22 10:34:48 2017

autotest: Clearly log the process of devserver health check.

As  shown, we don't have clear logs for how to iterate
devserver health check.

BUG= chromium:691009 
TEST=Ran unittest.

Change-Id: I155bdaaecb6b7f7e48abf028e7945cc950165f4e
Commit-Ready: Xixuan Wu <>
Tested-by: Xixuan Wu <>
Reviewed-by: Xixuan Wu <>


Comment 6 by, Jun 22 2017

Status: Fixed (was: Started)
Status: Archived (was: Fixed)

Sign in to add a comment