On Thu, 2012-06-14 at 11:58 -0400, Don Zickus wrote: > I was helping to debug install quirks that would write to the read-only > install path. I noticed a couple of directories were being written > and to fix them it was easier to consolidate some of the config options. > > The directories/files in particular were: > > /usr/lib/python-2.6/site-packages/autotest/tests/ > /usr/lib/python-2.6/site-packages/autotest/site_tests/ > /usr/lib/python-2.6/site-packages/autotest/control > > I realized they all have similar redirections to a > /var/lib/autotest/tests/ directory. > > So I decided to modify the code to assume that was the > output of the test results and just point everything there > if it was configured. > > As a result, the following options disappear: > > test_tmp_dir > pkg_dir > state_dir > > and are replaced with > > testout_dir > > I tested this by running as a non-root user and making the > /usr/lib/python-2.6.. > path read-only. These changes allowed things to work again from a client > perspective. The command I used was > > autotest-local run sleeptest > > with test_src_dir configured to point at my autotest git tree's client/test > directory.
That looks good Don, I'll do a bit of testing, but seems you've nailed it. > Signed-off-by: Don Zickus <[email protected]> > --- > > There is probably some blind ignorance with this patch as I didn't test with > the > autotest-remote command and other harnesses besides harness_standalone. I > also do not > know how to run the standalone testsuite. :-( utils/unittest_suite.py is what executes all unittests known to men. Well, you have to pass --full to execute them all, but the extra ones don't seem to be relevant here. > If anyone knows of an easy way to do some more test coverage I can run those > commands. > Though setting up the server will take some effort to download all the right > packages > and configure things. Not needed for now (I already have a vm setup ready here), but if one day you'd like to set up a server, this is what I do: 1) Install 2 VMs with Fedora (17 as of today). I do it using kvm autotest because it's fully automated and I'm very familiar with it, methods may vary. 2) Run the shell script we came up with to install the server in one of the VMs. This should do all the heavy lifting for you. https://github.com/autotest/autotest/wiki/KVMAutotest-GetStartedServer 3) Make sure the server vm can ssh as root passwordless in the other vm that will be the client 4) go to the admin interface (link top right corner of the web interface) and add the ip of the client vm there as one of the Hosts. There, all done. Thanks! _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
