On Wed, Nov 21, 2012 at 11:56:54AM +0100, Ján Tomko wrote:
> On 11/21/12 10:06, Daniel P. Berrange wrote:
> > On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
> >> On 11/20/12 20:36, Toralf Förster wrote:
> >>>
> >>> n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/test
On 11/21/12 10:06, Daniel P. Berrange wrote:
> On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
>> On 11/20/12 20:36, Toralf Förster wrote:
>>>
>>> n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests #
>>> VIR_TEST_DEBUG=1 ./virdrivermoduletest
>>> TEST: virdrivermo
On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
> On 11/20/12 20:36, Toralf Förster wrote:
> >
> > n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests #
> > VIR_TEST_DEBUG=1 ./virdrivermoduletest
> > TEST: virdrivermoduletest
> > 1) Test driver "storage"
On 11/20/12 20:36, Toralf Förster wrote:
>
> n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests #
> VIR_TEST_DEBUG=1 ./virdrivermoduletest
> TEST: virdrivermoduletest
> 1) Test driver "storage" ... OK
> 2) Test driver "nodedev"
On 11/19/2012 03:14 PM, Martin Kletzander wrote:
> On 11/11/2012 10:25 AM, Toralf Förster wrote:
>> I've a stable Gentoo Linux, the build log is attached.
>>
>
> It's hard to say from the log, but you can check yourselves what the
> problem is by running the particular test like this:
>
> VIR_TES
On 11/11/2012 10:25 AM, Toralf Förster wrote:
> I've a stable Gentoo Linux, the build log is attached.
>
It's hard to say from the log, but you can check yourselves what the
problem is by running the particular test like this:
VIR_TEST_DEBUG=1 ./virdrivermoduletest
in the tests/ directory after
