No prob, thanks for reporting!

OK, it seems it was either a glitch or my database was somehow corrupted.
IT works now. Sorry for the noise.

On Mon, Apr 18, 2016 at 1:20 PM, eyal edri [Administrator] (oVirt JIRA) <

We are still running dao tests [1], can you see if it was caught there?
You can actually see it failed yesterday [2].

There is an open TASK to move it also to STANDARD CI [3], would love to see someone from dev take it and finishing it.

[1] http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_created/
[2] source patch that started failing: http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_created/15317/
[3] https://ovirt-jira.atlassian.net/browse/OVIRT-450

OK, so it seems the basic tests are fine and this fails in DAO tests,
let me recreate my DB to see what happens.

On Mon, Apr 18, 2016 at 12:13 PM, Martin Sivak <msivak@redhat.com> wrote:
> The git hash is not the offending patch, just the HEAD where I found out.
>
> Martin
>
> On Mon, Apr 18, 2016 at 12:11 PM, Eyal Edri <eedri@redhat.com> wrote:
>> How did that pass jenkins tests?
>> Was the offending patch merged with -1?
>>
>> E.
>>
>> On Mon, Apr 18, 2016 at 1:09 PM, Martin Sivak <msivak@redhat.com> wrote:
>>>
>>> Hi,
>>>
>>> I just found out that I can't build the master branch
>>> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0) because of
>>>
>>> Tests in error:
>>>
>>> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
>>> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
>>>
>>>
>>>
>>> Martin
>>
>>
>>
>>
>> –
>> Eyal Edri
>> Associate Manager
>> RHEV DevOps
>> EMEA ENG Virtualization R&D
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)

Soo, then what you are asking is to find out which patch was the one that introduced the error?