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

Issue 705043 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Suite scheduler is hitting a ControlFileNotFound exception

Project Member Reported by pho...@chromium.org, Mar 24 2017

Issue description

03/24 12:33:32.128 ERROR|              task:1026| ControlFileNotFound: test_suites/control.android_telephony_nexus_tmo is not unique.
Traceback (most recent call last):
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 120, in dispatchRequest
    results['result'] = self.invokeServiceEndpoint(meth, args)
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 160, in invokeServiceEndpoint
    return meth(*args)
  File "/usr/local/autotest/frontend/afe/rpc_handler.py", line 270, in new_fn
    return f(*args, **keyword_args)
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 1161, in replacement
    return func(**kwargs)
  File "/usr/local/autotest/frontend/afe/rpc_interface.py", line 1942, in create_suite_job
    control_file = _get_control_file_by_suite(suite_name)
  File "/usr/local/autotest/frontend/afe/rpc_interface.py", line 1772, in _get_control_file_by_suite
    return getter.get_control_file_contents_by_name(suite_name)
  File "/usr/local/autotest/server/cros/dynamic_suite/control_file_getter.py", line 120, in get_control_file_contents_by_name
    raise error.ControlFileNotFound(test_name + ' is not unique.')
ControlFileNotFound: test_suites/control.android_telephony_nexus_tmo is not unique.
 

Comment 1 by pho...@chromium.org, Mar 24 2017

From chat, dshi@:

chromeos-server30 is used by suite scheduler as rpc server; it's not up to date.
I just forced a repo sync. if suite scheduler still reports the error, we can look further. It was on commit 78f61eab08cfb5cc1f88e585445fcee9437fc5d3, which is more than 10 days old

Comment 2 by dshi@chromium.org, Mar 24 2017

No more error since 03/24 12:39:27.681. I think the issue is fixed. will check in couple hours.

Comment 3 by dshi@chromium.org, Jun 12 2017

Status: Fixed (was: Available)

Comment 4 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment