Re: [ovirt-devel] [VDSM] vdsm_master_verify-error-codes_created running on master - why?

On Tue, Jul 19, 2016 at 6:20 PM, Eyal Edri wrote: > And also, feel free to move it to check-patch.sh code as well. Including this in vdsm seem like the best option. Can you point me to the source of this job? > > On Tue, Jul 19, 2016 at 6:19 PM, Eyal Edri

[ovirt-devel] [RFE][4.1][F24] Fedora 24 support

Hi, as you know Fedora 24 has been released last month. I pushed a pull request[1] describing the feature support effort. Of the detailied description, the following items have been already implemented: - Support building on Fedora 24 - Create Jenkins jobs for automated build and testing on

Re: [ovirt-devel] [VDSM] vdsm_master_verify-error-codes_created running on master - why?

And also, feel free to move it to check-patch.sh code as well. On Tue, Jul 19, 2016 at 6:19 PM, Eyal Edri wrote: > This isn't new, it was running for a few years, just on old jenkins, > Maybe you just noticed it. > > Allon & Dan are familiar with that job and it already found

Re: [ovirt-devel] [VDSM] vdsm_master_verify-error-codes_created running on master - why?

This isn't new, it was running for a few years, just on old jenkins, Maybe you just noticed it. Allon & Dan are familiar with that job and it already found in the past real issues. If you want to remove/disable it, I have no problem - just make sure you're synced with all VDSM people that

[ovirt-devel] Arrays.asList and GWT

Hi List, Seems like GWT can't handle Arrays.asList not very well. Sharing this in case others have similar issues: I was working on a very strange deserialization bug in combination with GWT [1]. We had a deserialization problem after loading a VM and trying to send the VM back to the backend.

Re: [ovirt-devel] execCmd() and storing stdout and stderr in log file

On Tue, Jul 19, 2016 at 5:07 PM, Yaniv Bronheim wrote: > > On Tue, Jul 19, 2016 at 4:56 PM, Tomáš Golembiovský > wrote: >> >> On Thu, 14 Jul 2016 17:25:28 +0300 >> Nir Soffer wrote: >> >> > After https://gerrit.ovirt.org/#/c/46733/

Re: [ovirt-devel] execCmd() and storing stdout and stderr in log file

On Tue, Jul 19, 2016 at 4:56 PM, Tomáš Golembiovský wrote: > On Thu, 14 Jul 2016 17:25:28 +0300 > Nir Soffer wrote: > > > After https://gerrit.ovirt.org/#/c/46733/ you should be able to create > > the pipeline in python like this: > > > > v2v =

Re: [ovirt-devel] execCmd() and storing stdout and stderr in log file

On Thu, 14 Jul 2016 17:25:28 +0300 Nir Soffer wrote: > After https://gerrit.ovirt.org/#/c/46733/ you should be able to create > the pipeline in python like this: > > v2v = Popen(["virt-v2v", ...], stdout=PIPE, stderr=STDOUT) > tee = Popen(["tee", "-a", logfile],

[ovirt-devel] oVirt 4.0.2 RC1 merge / branch / tag / bugzilla reminder

All stable branch maintainers, please make sure to - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release

[ovirt-devel] [ANN] oVirt 4.0.1 Final Release is now available

The oVirt Project is pleased to announce today the general availability of oVirt 4.0.1. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat