On Fri, Feb 24, 2017 at 8:52 PM, Nir Soffer wrote:
> On Fri, Feb 24, 2017 at 7:43 PM, Nir Soffer wrote:
>> On Fri, Feb 24, 2017 at 5:54 PM, Piotr Kliczewski
>> wrote:
>>> One more failure [1]
>>
>> I posted this:
>> https://gerrit.ovirt.org/73074
>>
>> Hopefully we can understand this failure be
On Fri, Feb 24, 2017 at 7:43 PM, Nir Soffer wrote:
> On Fri, Feb 24, 2017 at 5:54 PM, Piotr Kliczewski
> wrote:
>> One more failure [1]
>
> I posted this:
> https://gerrit.ovirt.org/73074
>
> Hopefully we can understand this failure better when we reproduce this with
> the
> data that fail the c
Sorry, but I really don't think this is the right direction to go.
This exposes check-patch to outside repos and may result in
repo-stability-related failures after we've made great efforts to eliminate
those.
This kind of test should really be done at the OST stage IMO.
בתאריך 24 בפבר׳ 2017 18:
On Fri, Feb 24, 2017 at 5:54 PM, Piotr Kliczewski
wrote:
> One more failure [1]
I posted this:
https://gerrit.ovirt.org/73074
Hopefully we can understand this failure better when we reproduce this with the
data that fail the checksum.
Nir
>
> [1]
> http://jenkins.ovirt.org/job/vdsm_master_che
On Fri, Feb 24, 2017 at 4:59 PM, Sandro Bonazzola
wrote:
> Hi,
> with the following commits:
> - https://gerrit.ovirt.org/71553
> - https://gerrit.ovirt.org/71623
>
> a minimal repository closure check is added to check-patches.sh.
> Instead of performing a full blown repository closure, I limite
Hi,
with the following commits:
- https://gerrit.ovirt.org/71553
- https://gerrit.ovirt.org/71623
a minimal repository closure check is added to check-patches.sh.
Instead of performing a full blown repository closure, I limited the check
to the built rpms in oreder to reduce the risk of hitting re
One more failure [1]
[1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/7610/console
On Mon, Feb 20, 2017 at 3:41 PM, Piotr Kliczewski
wrote:
> Nir,
>
> I saw this issue in [1]:
>
> 10:20:12 FAIL: test_send_receive (storage_mailbox_test.TestMailbox)
> 10:20:12
> ---
On Fri, Feb 24, 2017 at 11:58 AM, Sahina Bose wrote:
> Hi all,
>
> The ovirt-engine 4.1 appliance has the Default cluster set to 4.2 and the
> hyperconverged OST tests fail here as the 4.1 host cannot be added to
> cluster. (CLUSTER_VERSION_INCOMPATIBLE_WITH_CLUSTER)
>
> The appliance is from h
Hi all,
The ovirt-engine 4.1 appliance has the Default cluster set to 4.2 and the
hyperconverged OST tests fail here as the 4.1 host cannot be added to
cluster. (CLUSTER_VERSION_INCOMPATIBLE_WITH_CLUSTER)
The appliance is from
http://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/noarch/o
