Im attempting to run via the lago commands re Barak's suggestion, but I'm running into ssh timeouts (as it seems like maybe a failing deployment)
myoung at dev-vm in ~/repos/github/ovirt-system-tests/vagrant on master*
$ lago deploy
@ Deploy environment:
  # [Thread-2] Deploy VM lago-vagrant-host-0:
  # [Thread-1] Deploy VM lago-vagrant-engine:
    * [Thread-2] Wait for ssh connectivity:
    * [Thread-1] Wait for ssh connectivity:
    * [Thread-2] Wait for ssh connectivity: ERROR (in 0:28:21)
  # [Thread-2] Deploy VM lago-vagrant-host-0: ERROR (in 0:28:21)

With no changes,  using `run_suite.sh`, however, it works fine:

...snip....
/home/myoung/repos/github/ovirt-system-tests
@ Deploy oVirt environment:
  # Deploy environment:
    * [Thread-2] Deploy VM lago-vagrant-engine:
    * [Thread-3] Deploy VM lago-vagrant-host-0:
    * [Thread-3] Deploy VM lago-vagrant-host-0: Success (in 0:00:44)
    * [Thread-2] Deploy VM lago-vagrant-engine: Success (in 0:13:16)
  # Deploy environment: Success (in 0:13:16)
@ Deploy oVirt environment: Success (in 0:13:16)
/home/myoung/repos/github/ovirt-system-tests
Running test scenario 000_check_repo_closure.py
@ Run test: 000_check_repo_closure.py:
....snip....

and even continues to a full suite success:
@ Collect artifacts: Success (in 0:00:04)
/home/myoung/repos/github/ovirt-system-tests
run_suite.sh::main::SUCCESS:: /home/myoung/repos/github/ovirt-system-tests/vagrant - All tests passed :)

Is there a lago command I'm missing/some sort of configuration change needed that I'm missing to run the lago commands manually?
I've been trying to piece together the manual commands from run_suite.sh but I dont see it doing anything that I'm outright missing.

On Sat, Sep 16, 2017 at 2:27 PM, Nadav Goldin <ngoldin@virtual-gate.net> wrote:
Hi,
Rerunning a specific python test file is possible, though it takes few
manual steps. Take a look at [1].

With regard to the debugger, it is possible to run the tests without
'lago ovirt runtest' commands at all, directly with Lago as a Python
library, though it isn't fully used in OST. Basically you would have
to export the same environment variables as described in [1], and then
use the same imports and decorators as found in OST(mainly the
testlib.with_ovirt_prefix decorator), with that in hand you can call
the python file however you'd like.

Of course this is all good for debugging, but less for OST(as you need
the suite logic: log collections, order of tests, etc).



[1] http://lists.ovirt.org/pipermail/lago-devel/20170402/000650.html

On Thu, Sep 14, 2017 at 8:59 PM, Marc Young <3vilpenguin@gmail.com> wrote:
> Is it possible to run a specific scenario without having to run back through
> spin up/tear down?
>
> I want to rapidly debug a `test-scenarios/00#_something.py` and the
> bootstrap scripts (001,002) take a really long time.
>
> Also is it possible to attach to a debugger within the test-scenario with
> pdb? I didnt have luck and it looks like its abstracted away and not
> executed as a regular python file in a way that i can get to an interactive
> debugger
>
> _______________________________________________
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel