[ovirt-devel] vdsm check patch failed on loopback.py#test_with_device

Hi, Jenkins check-patch job is failing on: === FAILURES === 15:19:02 test_with_device[4096] 15:19:02 15:19:02 tmpdir = local('/var/tmp/vdsm/test_with_device_4096_0'),

[ovirt-devel] Re: planned Jenkins restart

Maintenance completed, Jenkins is up and running. OS updates along with performance tweaks were applied this time. As always - if you see any issues please report them to Jira. Regards, Evgheni Dereveanchin On Thu, Sep 26, 2019 at 12:07 AM Evgheni Dereveanchin wrote: > Hi everyone, > > I'll

[ovirt-devel] planned Jenkins restart

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin ___ Devel mailing list --

[ovirt-devel] Re: IMPORTANT: OST is now gated.

Ehud Yonasi writes: > Hey everyone, > OST project is now enabled for patch gating. Hi, it's cool, but before enabling it for other projects, please make sure pending OST problems are fixed. AFAIK the random failures related to add_master_storage_domain in basic-suite-master and discussed here

[ovirt-devel] Re: Patch Gating summary + FAQ

> On 22 Sep 2019, at 09:33, Barak Korren wrote: > > > > On Thu, 19 Sep 2019 at 17:13, Ehud Yonasi > wrote: > Hey everyone, > Following the presentation we did last week [1] > , I wanted to summarize the new patch gating > workflow

[ovirt-devel] Re: IMPORTANT: OST is now gated.

On Wed, Sep 25, 2019 at 2:07 PM Tal Nisan wrote: > > > On Wed, Sep 25, 2019 at 1:54 PM Ehud Yonasi wrote: > >> Hey everyone, >> OST project is now enabled for patch gating. >> >> What is the meaning of this? >> >>1. The gating process will start when Code-Review +2, CI +1 and >>Verified

[ovirt-devel] Re: IMPORTANT: OST is now gated.

On Wed, Sep 25, 2019 at 1:54 PM Ehud Yonasi wrote: > Hey everyone, > OST project is now enabled for patch gating. > > What is the meaning of this? > >1. The gating process will start when Code-Review +2, CI +1 and >Verified +1 labels are turned on. >2. Every patch before merging will

[ovirt-devel] Re: CI is not triggered for pushed gerrit updates

This is a known issue - tacker ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2802 Will close new ticket as a duplicate On Wed, 25 Sep 2019 at 13:08, Nir Soffer wrote: > On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer wrote: > >> CI has stopped from being triggered for pushed gerrit

[ovirt-devel] IMPORTANT: OST is now gated.

Hey everyone, OST project is now enabled for patch gating. What is the meaning of this? 1. The gating process will start when Code-Review +2, CI +1 and Verified +1 labels are turned on. 2. Every patch before merging will have to pass the following suites: - *oVirt-master*

[ovirt-devel] Re: CI is not triggered for pushed gerrit updates

On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer wrote: > CI has stopped from being triggered for pushed gerrit updates. > Adding infra-suppo...@ovirt.org - this file a bug in infra bug tracker. Example at: https://gerrit.ovirt.org/#/c/103320/ > last PS did not trigger CI tests. > More examples:

[ovirt-devel] Re: CI is not triggered for pushed gerrit updates

sorry, missed earlier mail reporting this is already resolved. On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer wrote: > CI has stopped from being triggered for pushed gerrit updates. > > Example at: https://gerrit.ovirt.org/#/c/103320/ > last PS did not trigger CI tests. > > Please advise. >

[ovirt-devel] CI is not triggered for pushed gerrit updates

CI has stopped from being triggered for pushed gerrit updates. Example at: https://gerrit.ovirt.org/#/c/103320/ last PS did not trigger CI tests. Please advise. ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to

[ovirt-devel] Re: PROBLEM: Issue has been detected with gerrit trigger.

The problem has been resolved. Regard, Ehud. On Wed, Sep 25, 2019 at 12:17 PM Ehud Yonasi wrote: > Update: > We are planning to restart Jenkins in the next minutes, please do not use > the manual trigger. > > On Wed, Sep 25, 2019 at 12:07 PM Ehud Yonasi wrote: > >> Hey everyone, >> A problem

[ovirt-devel] Re: PROBLEM: Issue has been detected with gerrit trigger.

Update: We are planning to restart Jenkins in the next minutes, please do not use the manual trigger. On Wed, Sep 25, 2019 at 12:07 PM Ehud Yonasi wrote: > Hey everyone, > A problem was identified that causes the CI not working with gerrit > patches. > We are working on fixing the automatic

[ovirt-devel] PROBLEM: Issue has been detected with gerrit trigger.

Hey everyone, A problem was identified that causes the CI not working with gerrit patches. We are working on fixing the automatic triggering and bringing it online asap. We are sorry for the inconvenience at the moment. If you want to run the CI for your patch atm you can use the manual gerrit