--5L6AZ1aJH5mDrqCQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 09/17, Francesco Romani wrote:
----- Original Message -----
> From: "David Caro" <dcaro(a)redhat.com>
> To: "Francesco Romani" <fromani(a)redhat.com>
> Cc: "infra" <infra(a)ovirt.org>
> Sent: Thursday, September 17, 2015 3:47:44 PM
> Subject: Re: How to remove bad Jenkins CI score
>=20
> On 09/17, Francesco Romani wrote:
> > ----- Original Message -----
> > > From: "David Caro" <dcaro(a)redhat.com>
> > > To: "Francesco Romani" <fromani(a)redhat.com>
> > > Cc: "infra" <infra(a)ovirt.org>
> > > Sent: Thursday, September 17, 2015 3:38:24 PM
> > > Subject: Re: How to remove bad Jenkins CI score
> > >=20
> >=20
> > > > > You can see the full test output here:
> > > > >
http://jenkins.ovirt.org/job/vdsm_3.6_check-patch-fc22-x86_64/3=
7/console
> > > > > The new invocation is still running ATM
here:
> > > > >
http://jenkins.ovirt.org/job/vdsm_3.6_check-patch-fc22-x86_64/7=
4/console
> > > >=20
> > > > Thanks! But the old score is still here, despite
> > >=20
> > >=20
> > > That's because the +1 is for the patchset 1, and the -1 is on patch=
set 3
> > > (it
> > > was carried over from patchset 1 because the 2 and 3 did no code ch=
anges)
> > >=20
> > > The jobs don't trigger for patches that don't change any code, and
=
as
> > > such,
> > > it
> > > does not update the value for patch 3.
> > > The only way to allow that would be to trigger on any patch, but th=
at
> > > would
> > > overload jenkins.
> >=20
> > Yes, that makes sense.
> >=20
> > > In any case, it should not be blocking anything.
> >=20
> > Well, in this unfortunate case of one bogus/temporary initial failure=
yes,
> > because
> > I don't have the "submit" button on my screen :\
>=20
> You are not part of the maintainers for that branch (same as master)
>=20
>
https://gerrit.ovirt.org/#/admin/groups/31,members
=20
Sorry, I don't follow.
I already merged patches[0] in vdsm ovirt-3.6, and I have the submit butt=
on[1]
in the screen of the following patch of the same branch[2].
My bad, you are as you should, it turns out that the flag is wrongly config=
ured
specifycally on vdsm (as we did not roll out the whole flags initiative, it=
got
'half deployed').
I've just changed it, hit f5
=20
Please check the attached screenshot
=20
+++
=20
[0] last example:
https://gerrit.ovirt.org/#/c/46102/
[1] Unless it is a trap :)
[2] but I don't want to merge them out of order
=20
--=20
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web:
www.redhat.com
RHT Global #: 82-62605
--5L6AZ1aJH5mDrqCQ
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV+sgBAAoJEEBxx+HSYmnDQgkH/26TSuYJi7GUSiM58QJHlv/1
1Z3vepRBmqJyZvpwYb/PhAw1HrxKqcU0tXINp/WsPRK6JknjyVb9mT6B0rgT+N9Q
JFkdwOSVhMbmKRsjeBEApjh7djXHRKqRWZgmD+cy7MR1j3UunKX0QklapSqmcmWP
rWE/9bpvFm7zHB2Il7mN8ccuREQ4vCT3XYEyMCilU+rx8hQchtgzVOVXiVFtHwOb
j6FTCgxo+IlThBUQwav6ijh70SNzpDKeIjcdir715yHJ8FP+o1eh+H4qXZWM1fsy
uqroWScic+0bPJPl+aKl86/WLXR6cYmJsVtP+/q/FtT1c4TiFodzuP/8NknsJ6Q=
=CxK6
-----END PGP SIGNATURE-----
--5L6AZ1aJH5mDrqCQ--