Wow! Thank you. On Thu, Feb 9, 2017 at 9:31 AM, Lukáš Doktor <ldok...@redhat.com> wrote:
> Dne 8.2.2017 v 17:54 Andrei Stepanov napsal(a): > >> Hi. >> >> I am trying to run avocado in virtualenv. Avocado ignores data_dir in >> global config. >> >> (virtualenv) -bash-4.2# avocado --version >> Avocado 45.0 >> >> >> (virtualenv) -bash-4.2# cat /etc/avocado/avocado.conf >> [datadir.paths] >> > Hello Andrei, > > when you're inside virtualenv the `avocado.conf` comes from the virual-env > path (eg: `venv/etc/avocado/avocado.conf`). I tried it and it worked well > on my machine. Also note that some of the dirs have to be writable by the > user (logs and data if I'm not mistaken), otherwise avocado uses default > path instead. To check which data dirs are in use by the current user you > can run `avocado config --datadir` ;-) > > Regards, > Lukáš > > > data_dir = /mnt/tests/spice/qe-tests/avocado-data >> logs_dir = /mnt/tests/spice/qe-tests/avocado-logs >> >> >> (virtualenv) -bash-4.2# avocado vt-bootstrap --vt-type qemu >> --vt-no-downloads --vt-update-config >> >> >> It uses: /usr/share/avocado/data >> >> >> 17:51:11 INFO | 5 - Generating config set >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/base.cfg exists, >> equal t >> o sample >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/cdkeys.cfg exists, >> equal >> to sample >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/guest-hw.cfg >> exists, equ >> al to sample >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/machines.cfg >> exists, equ >> al to sample >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/virtio-win.cfg >> exists, e >> qual to sample >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/subtests.cfg auto >> genera >> ted from subtest samples >> 17:51:11 DEBUG| Config file >> /usr/share/avocado/data/avocado-vt/backends/qemu/cfg/guest-os.cfg auto >> genera >> ted from guest OS samples >> >> >> Any ideas how to fix this? >> > >
