Ok the root cause of the false verify +1 is very simple. It was verified on May 09 against a very old tree. https://build.opnfv.org/ci/job/releng-jjb-verify/1369/
Else most of the patches were voted -1 due to the failure when locking cache. https://build.opnfv.org/ci/job/releng-jjb-verify/1584/console triggered by https://gerrit.opnfv.org/gerrit/c/releng/+/69327 Cédric On Sat, 2019-12-14 at 14:08 -0500, Aric Gardner wrote: > Cedic, I don't understand what you mean > > The patchset that caused the problem was reverted. > here: https://gerrit.opnfv.org/gerrit/c/releng/+/69343 > and your patchset was rebased and is verified and ready to submit > here. > https://gerrit.opnfv.org/gerrit/c/releng/+/69334 > > On Sat, Dec 14, 2019 at 4:57 AM <ollivier.ced...@gmail.com> wrote: > > > > From my understanding, they are multiple issues here. > > > > The jjb shouldn't have be merged and the merge error is pretty > > clear > > How was it verified by the jjb linter? Classical falsy Releng > > recheck > > or reverify? > > > > 13:29:45 yaml.composer.ComposerError: found undefined alias > > 'gambia' > > https://build.opnfv.org/ci/job/releng-jjb-merge/861/ > > > > Yes, all next patches will be rated -1 but we can't reach this step > > because the cache is locked. > > > > @Aric: Would you mind removing the lock on jjb cache first (nobody > > can't do it out of LF)? and then reverting this change breaking > > master? > > > > Cédric > > > > On Fri, 2019-12-13 at 19:57 -0500, Aric Gardner wrote: > > > It was actually this change, that failed jjb-merge > > > > > > https://gerrit.opnfv.org/gerrit/c/releng/+/67813 > > > > > > that is breaking future commits. > > > > > > I will look at it tomorrow. > > > > > > > > > On Fri, Dec 13, 2019 at 5:28 PM Cedric OLLIVIER > > > <ollivier.ced...@gmail.com> wrote: > > > > > > > > Hi, > > > > > > > > I think a few people have faced with Releng issues for the last > > > > days > > > > when creating their stable branches. The problem is linked to > > > > releng- > > > > jjb-verify which seems defined out of OPNFV via submodule [1] > > > > (hoping > > > > I'm wrong as all OPNFV projects would depend on it) or to the > > > > build > > > > host. > > > > > > > > jenkins_jobs.errors.JenkinsJobsException: Unable to lock > > > > cache > > > > for ' > > > > https://build.opnfv.org/ci' > > > > > > > > Please don't call reverify/recheck because the second > > > > verification > > > > seems incorrect due to wrong triggers and could postpone bigger > > > > issues. > > > > https://gerrit.opnfv.org/gerrit/c/releng/+/69334 > > > > > > > > Can someone manage this issue? > > > > And who, from OPNFV active members and out of LF, can merge in > > > > lfit/releng-global-jjb? > > > > > > > > [1] > > > > > > > > https://github.com/lfit/releng-global-jjb/blob/v0.35.0/jjb/lf-ci-jobs.yaml#L898 > > > > > > > > Cédric > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- > > > > Links: You receive all messages sent to this group. > > > > > > > > View/Reply Online (#23781): > > > > https://lists.opnfv.org/g/opnfv-tech-discuss/message/23781 > > > > Mute This Topic: https://lists.opnfv.org/mt/68554822/1009618 > > > > Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org > > > > Unsubscribe: > > > > https://lists.opnfv.org/g/opnfv-tech-discuss/unsubb [ > > > > agard...@linuxfoundation.org] > > > > -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23788): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23788 Mute This Topic: https://lists.opnfv.org/mt/68554822/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
