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

Issue 625245 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

git_nyc-jaqen-dev/jaqen_edison-userdebug/3026572 is a malformed build name

Project Member Reported by sbasi@chromium.org, Jul 1 2016

Issue description

I tried to create a suite via the UI:

ParseBuildNameException: git_nyc-jaqen-dev/jaqen_edison-userdebug/3026572 is a malformed build name.
Traceback (most recent call last):
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 114, in dispatchRequest
    results['result'] = self.invokeServiceEndpoint(meth, args)
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 154, in invokeServiceEndpoint
    return meth(*args)
  File "/usr/local/autotest/frontend/afe/rpc_handler.py", line 125, in new_fn
    return f(*args, **keyword_args)
  File "/usr/local/autotest/frontend/afe/rpc_interface.py", line 938, in create_job_page_handler
    is_cloning=is_cloning, **kwargs)
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 1339, in replacement
    return func(**kwargs)
  File "/usr/local/autotest/frontend/afe/site_rpc_interface.py", line 269, in create_suite_job
    board = utils.ParseBuildName(builds[provision.CROS_VERSION_PREFIX])[0]
  File "/usr/local/autotest/server/site_utils.py", line 86, in ParseBuildName
    raise ParseBuildNameException('%s is a malformed build name.' % name)
ParseBuildNameException: git_nyc-jaqen-dev/jaqen_edison-userdebug/3026572 is a malformed build name.


But it works via run_suite:
$ ./site_utils/run_suite.py --pool=cq --timeout_mins=30 --suite_name=brillo-presubmit --board=edison --build=git_nyc-jaqen-dev/jaqen_edison-userdebug/3026572
Autotest instance: cautotest
07-01-2016 [11:56:31] Submitted create_suite_job rpc
07-01-2016 [11:56:41] Created suite job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=68226657
@@@STEP_LINK@Link to suite@http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=68226657@@@


Dan can you verify we haven't broken testbed support...?
 

Comment 1 by sbasi@chromium.org, Jul 1 2016

Good news is that I can create single test jobs from the AFE.

Maybe we never supported Android/Brillo suites from the UI? I can't remember but I thought this worked...

Comment 2 by sbasi@chromium.org, Jul 1 2016

Cc: dshi@chromium.org
Owner: sbasi@chromium.org
I'll take a look at why this is broken if single jobs are working.
Status: Assigned (was: Untriaged)

Sign in to add a comment