> > By default, the tests are copied on demand, so the tests will be
> > installed to the machine running autoserv as they are needed on the
> > control file. As I can see you are trying to execute the 'selftest'
> > client control file. So as long as the autotestd_monitor problem is
> > solved, autoserv will compress the contents of selftest and copy it to
> > the client. If you want all tests to be copied to your client (not
> > really recommended), you can modify in global_config.ini the following
> > config
> >
>
>
I have found the error. One is in autotestd_monitor file line 19:
---------
argv = ['tail', '--retry', '--follow=name', '--bytes=+%d' % start, path]
---------
My board doesn't support tail '--' option, so I change it to :
--------
argv = ['tail', '-f', '-c', '+%d' % start, path]
-------
In best situation, I should replace '--rerty --follow=name' with '-F'
option, however, my board doesn't support -F either. Will '-f' produce any
side effect?
The other error is in client/common-lib/base_package.py line 800:
--------
self._run_command('tar xjf %s -C %s' % (tarball_path, dest_dir))
--------
The 'j' option isn't supported, I change the command to:
----------
bunzip2 -c tarball_path | tar xf - -C dest_dir
----------
The lase fix is in server/autotest.py. I delete all "nohup" because my board
doesn't support this command.....
Now the selftest can run well, but I don't know whether such fixes will
bring in some bug.
--
Zhu Chenjie
Zhejiang University, China
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
