--jIYo0VRlfdMI9fLa Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 06/18, Eyal Edri wrote:

=20 =20 ----- Original Message -----

...

From: "Shmuel Melamud" <smelamud@redhat.com> To: infra@ovirt.org Sent: Thursday, June 18, 2015 1:25:35 PM Subject: Verified-1 is set to backported patch if original patch wasn't= merged yet =20 Hi! =20 I'm working on this patch https://gerrit.ovirt.org/#/c/42538/ which is backport to 3.5 of this patch https://gerrit.ovirt.org/#/c/42392/. When= I've submitted the backported patch, the original patch wasn't yet merged in= to master and I got the following message: =20 gerrit-hooks Patch Set 1: Verified-1 =20 Update tracker::#1232419::OK Check Bug-Url::OK Check Public Bug::#1232419::OK, public bug Check Product::#1232419::OK, Correct product Red Hat Enterprise Virtualization Manager Check TR::#1232419::OK, correct target release 3.5.4 Check merged to previous::WARN, Still open on branches master =20 Is it correct? Why it sets Verified-1 here? (CI+1 was set after success= ful build) =20 looks like a bug in gerrit hooks, david - is it a known issue?

The hooks are not related to jenkins (just to be clear). The issue here is = that the patch was not yet merged to master, any backported patch should be merg= ed to master *before* getting it merged to any stable branch. If the patch is already merged to master you can retrigger the hooks to cle= ar the -1 with a comment on gerrit that starts with:=E7=20 Rerun-Hooks: all

...

=20 -- Shmuel _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra =20 =20 =20 =20 --=20 Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel =20

=20 phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --jIYo0VRlfdMI9fLa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVgsXKAAoJEEBxx+HSYmnDznoH/jyeMMWaVotMQeXbFAUFDYAV SgOF4XSwqybzvn9PQRwtyh6fIaao16SVVTPoQmIGCe+8KJ1Lmxq1z/xCFziLfACF ALvl87tJao99FrlZCxCrrhtZQWUxKlMqbqQI1F+oJVA9ZNJhsAxSU7hY6zm/4Bow ELvoNPM+xfnknddGjHqUn4/B0LoE2Iw6fgv3rI54JnmihvvugeAcEutVbb/oJUXQ bZGd9kgZIaFGxX0TdswMURbAfj2l9EOwgKZd42hsYr7dPbkFicl6lpnHHEmWvUGi g99cpi0H0r8QcenwVH3EUsyYYW8aShfCzTtIw/oiZ1XmBuNm7juJtSb+kHbyaIk= =wQcf -----END PGP SIGNATURE----- --jIYo0VRlfdMI9fLa--