On 19 October 2017 at 10:50, Allon Mureinik <amureini(a)redhat.com> wrote:
The missing deps issue happened again this morning [1]:
Why are you looking at OST check-patch job? it has little to do with how
OST runs when it is used to check other projects (For example it runs all
suits as opposed to just the stable ones, and it does not use or repo
protection mecahnisms...). Also that particular patch plays with repo
configuration so it is expected to fail on repo issues...
OST is stable ATM for all projects except engine, here are some passing
examples:
-
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
-
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
-
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
I think that is strong enough evidence that the issue is in engine code and
not in OST/repos/other places people like to point to.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. |
redhat.com/trusted