Hi folks,
I was going over the list of test modules we have, and found that the
cpuset_tasks bug module control file does reference a job method that is
not present, at least on the upstream (trunk) version of the job code:
{{{
NAME = "cpuset tasks bug"
AUTHOR = "Divyesh Shah ([email protected])"
TEST_TYPE = "client"
TEST_CLASS = "Kernel"
TEST_CATEGORY = "Functional"
TIME = "SHORT"
DOC = """\
This is a functional test for the bug where reading a cpuset's tasks
file would
fail with ENOMEM when a large number of tasks are present in that
cpuset.
"""
cont_args = {'cpus': [0, 1, 2, 3],
'mbytes': 3000,
'root': '',
'name': 'autotest_container'}
job.new_container(**cont_args)
job.run_test('cpuset_tasks')
job.release_container()
}}}
10:07:52 ERROR| JOB ERROR: Unhandled AttributeError: 'job' object has no
attribute 'new_container'
Traceback (most recent call last):
File "/usr/local/autotest/bin/job.py", line 1027, in _run_step_fn
exec('__ret = %s(*__args, **__dargs)' % fn, local_vars, local_vars)
File "<string>", line 1, in <module>
File "/usr/local/autotest/control.autoserv", line 24, in step0
job.new_container(**cont_args)
AttributeError: 'job' object has no attribute 'new_container'
10:07:52 DEBUG| Persistent state variable __group_level now set to 0
10:07:52 INFO | END ABORT ---- ---- timestamp=1274364472
localtime=May 20 10:07:52 Unhandled AttributeError: 'job' object has no
attribute 'new_container'
Traceback (most recent call last):
File "/usr/local/autotest/bin/job.py", line 1027, in _run_step_fn
exec('__ret = %s(*__args, **__dargs)' % fn, local_vars, local_vars)
File "<string>", line 1, in <module>
File "/usr/local/autotest/control.autoserv", line 24, in step0
job.new_container(**cont_args)
AttributeError: 'job' object has no attribute 'new_container'
So, please advise what is the intended fix for this issue.
Cheers,
Lucas
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
