[ovirt-devel] [VDSM] Broken test - testV2VOutput

[Dan Kenigsberg]

On Sun, Sep 04, 2016 at 11:39:07PM +0300, Nir Soffer wrote:
> Hi all,
> 
> The following test fails consistently, looks like bad test, running
> real v2v instead of the fake-v2v script.
> 
> Last change in this area was
> 
> commit 985cbe87077512adf1ff594841b7f79674d451fc
> Author: Tomáš Golembiovský <tgolembi at redhat.com>
> Date:   Wed Jun 22 15:21:26 2016 +0200
> 
>     v2v: Log detailed output of virt-v2v
> 
>     The detailed log of virt-v2v output is often necessary to debug
>     conversion failures. We provide '-v -x' arguments to virt-v2v to get the
>     detailed output and store the logs in the VDSM log directory.
> 
>     We cannot use execCmd() to store the log output. Therefore we use CPopen
>     directly to redirect stderr to stdout and pipe it to tee to store
>     everything in a log file.
> 
>     Logs older than 30 days are removed periodically on the daily basis.
> 
> Please fix or disable this test.

Tomas, I'm guessing that

https://gerrit.ovirt.org/63273 tests: unbreake testV2VOutput

would do the trick, but I did not test that.
Could Jenkins run the unit test from the distributed tarball to catch
such omissions?

> 
> ======================================================================
> ERROR: testV2VOutput (v2vTests.v2vTests)
> ----------------------------------------------------------------------