On Tue, 2011-12-06 at 07:05 -0500, Kamil Paral wrote:
> Reviewed, can be shipped IMHO.
>
> BTW: reviewboard ends with HTTP 500 error code after login, what is
> the best place to report it?
I guess it might be relevant to the recent invalidation of FAS passwords :-) Let's
bug RB maintainers about it. Any idea who that is?
Instead of adding a new label to all machines, it would be handy if
atest supported the wildcard completely. For example...
The following atest command accepts a wildcard ...
$ atest host list -b "*"
While job creation doesn't fully support the wildcard ...
$ atest job create -g -m "*" ...
Operation create_job failed:
ValidationError: {'meta_hosts': 'Label "" not found'}
Traceback (most recent call last):
File "/usr/share/autotest/frontend/afe/json_rpc/serviceHandler.py",
line 96, in dispatchRequest
results['result'] = self.invokeServiceEndpoint(meth, args)
File "/usr/share/autotest/frontend/afe/json_rpc/serviceHandler.py",
line 134, in invokeServiceEndpoint
return meth(*args)
File "/usr/share/autotest/frontend/afe/rpc_handler.py", line 120, in
new_fn
return f(*args, **keyword_args)
File "/usr/share/autotest/frontend/afe/rpc_interface.py", line 527, in
create_job
**rpc_utils.get_create_job_common_args(locals()))
File "/usr/share/autotest/frontend/afe/rpc_utils.py", line 710, in
create_job_common
{'meta_hosts' : 'Label "%s" not found' % label_name})
ValidationError: {'meta_hosts': 'Label "" not found'}
It's been working for our "noarch" style tests using a wildcard of
"*x86_64". But having just a splat, results in the above traceback.
Not having fully investigated 'atest job create', it seems like this is
a bug worth fixing. Either rpc_utils.py create_job_common() (or it's
callers) isn't properly handling a wildcard label. If that worked,
noarch job scheduling might require fewer changes on our end.
Thanks,
James