Re: [ovirt-devel] Subject: [ OST Failure Report ] [ oVirt master ] [ 26.11.17 ] [ 001_initialize_engine ]

2017-11-27 Thread Allon Mureinik
On Mon, Nov 27, 2017 at 2:30 PM, Allon Mureinik wrote: > The analysis is completely wrong. > > The offending patch is [1]. I assume the reason for the failure is that > gap between when the CI passed (Nov 21) and when it was merged (Nov 26). In > the five days in between,

Re: [ovirt-devel] Subject: [ OST Failure Report ] [ oVirt master ] [ 26.11.17 ] [ 001_initialize_engine ]

2017-11-27 Thread Allon Mureinik
The analysis is completely wrong. The offending patch is [1]. I assume the reason for the failure is that gap between when the CI passed (Nov 21) and when it was merged (Nov 26). In the five days in between, other patches entered master and invalidated this CI result. To quote the job's log: """

[ovirt-devel] Subject: [ OST Failure Report ] [ oVirt master ] [ 26.11.17 ] [ 001_initialize_engine ]

2017-11-26 Thread Gal Ben Haim
Suspected patches: https://gerrit.ovirt.org/#/c/84618/2 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4158/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4158/artifact/exported-artifacts/basic-suit-master-el7/ Error snippet from