>
>On Thursday, 3 January 2019 08:10:14 -02 Tony Sarajärvi wrote:
>> openNebula uses QEMU that uses libvirt to create a VM using KVM:
>Despite the name, in this mode QEMU is not emulating anything. When assisted
>by KVM this is real hardware virtualisation >and qemu only serves to provide
>the v
On Thursday, 3 January 2019 08:10:14 -02 Tony Sarajärvi wrote:
> openNebula uses QEMU that uses libvirt to create a VM using KVM:
Despite the name, in this mode QEMU is not emulating anything. When assisted
by KVM this is real hardware virtualisation and qemu only serves to provide
the virtual H
>On Wednesday, 2 January 2019 04:34:43 -02 Tony Sarajärvi wrote:
>> agent:2019/01/01 20:15:26 build.go:193: Config: Using QtTest library
>> 5.12.0, Qt 5.12.0 (x86_64-little_endian-lp64 shared (dynamic) release
>> build; by GCC
>> 5.3.1 20160406 (Red Hat 5.3.1-6))
>This is a native x86-64 build
On Wednesday, 2 January 2019 04:34:43 -02 Tony Sarajärvi wrote:
> agent:2019/01/01 20:15:26 build.go:193: Config: Using QtTest library 5.12.0,
> Qt 5.12.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC
> 5.3.1 20160406 (Red Hat 5.3.1-6))
This is a native x86-64 build and run. I
Hi
I'd like to know your opinion about these failures we've been seeing during the
last 24 hours. Are they related to QEMU being updated perhaps?
on RHEL 7.4:
agent:2019/01/01 20:15:25 build.go:193: /home/qt/work/install/bin/qmltestrunner
agent:2019/01/01 20:15:26 build.go:193: * Start t
Good morning.
Since our last verifications of 3 main branches show green light to make the
upgrade of the CI, I'll go ahead and proceed right away. The switch over will
only take seconds, and I'll start monitoring the system today to see that it
actually works.
What changes:
* Our hosts r
