On Wed, 2 Oct 2019 at 14:22, Eyal Edri <[email protected]> wrote:

>
>
> On Mon, Sep 30, 2019 at 11:19 AM Martin Perina <[email protected]> wrote:
>
>> Hi,
>>
>> as Didi mentioned in relevant email thread "[ovirt-devel] [ACTION
>> REQUIRED] unicode patches merged, update otopi" both otopi and ovirt-engine
>> must be updated to latest version. So most probably both otopi and
>> ovirt-engine have to go though CQ at once.
>>
>
> Can you specify which patches for engine and otopi must run together?
> Barak, can you help Dusan with running both patches together? should both
> use 'ci re-merge' together?
>
>

Generally if the queue is not empty and there are no regression - doing
re-merge for both at once would work (btw, if the builds are not too old,
rerunning a queue `add` build is enough, and it can skip building)

if the queue is empty:
1. re-add the 1st one - it will start being tested on its own (and will
fail)
2. re-add the 1st one again (it will wait for the running test to finish)
3. re-add the 2nd one (both will wait in the queue and therefore be tested
together)




>
>> M.
>>
>> On Sat, Sep 28, 2019 at 11:43 PM Dusan Fodor <[email protected]> wrote:
>>
>>> Hello all,
>>> initialize_engine test fails in CQ due to utf8/unicode type mismatch in
>>> engine-setup/ answer file:
>>> [ ERROR ] Failed to execute stage 'Clean up': must be unicode, not str
>>>
>>> The suspected change:
>>> https://gerrit.ovirt.org/#/c/102934/
>>>
>>> Failed job example:
>>>
>>> https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/16110
>>> <https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/16110/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/>
>>>
>>> Can you please this?
>>> Thanks
>>> _______________________________________________
>>> Devel mailing list -- [email protected]
>>> To unsubscribe send an email to [email protected]
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/[email protected]/message/CA2OUDAWZPWLSEASQOP6AUZ3MK6PP6JV/
>>>
>>
>>
>> --
>> Martin Perina
>> Manager, Software Engineering
>> Red Hat Czech s.r.o.
>> _______________________________________________
>> Devel mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/[email protected]/message/RYG7BQMTZ6CYRND3GQ45EBBAVEJMUTVE/
>>
>
>
> --
>
> Eyal edri
>
> He / Him / His
>
>
> MANAGER
>
> CONTINUOUS PRODUCTIZATION
>
> SYSTEM ENGINEERING
>
> Red Hat <https://www.redhat.com/>
> <https://red.ht/sig>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
>


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/C5S6K33XBCXOD6QXXX67D7Q2M7YUP4BH/

Reply via email to