Hi All, It looks like since [1] commit was merged to master the [2] became stale as it refers to findbugs-general maven profile that doesn't exist anymore. Infra team, please update [2] asap, as it faulty marks all patches as -1. [1] https://gerrit.ovirt.org/#/c/48687 [2] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_gerrit Regards, Yevgeny
On 06/20/2016 06:02 PM, Yevgeny Zaspitsky wrote:
Hi All,
It looks like since [1] commit was merged to master the [2] became stale as it refers to findbugs-general maven profile that doesn't exist anymore.
Infra team, please update [2] asap, as it faulty marks all patches as -1.
[1] https://gerrit.ovirt.org/#/c/48687 [2] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_gerrit
Regards, Yevgeny
The fact that the job uses a profile that doesn't exist shouldn't be problematic, it will just cause a warning. It would be good to remove that "-Pfindbugs-general" option anynow, to avoid the warning. I see the job running correctly for many patches. Do you have an example of a patch where it voted -1 incorrectly? -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
Sorry, my conclusion was too hasty. Juan, you're right - that's my patch fault. All failures I saw were caused by a single faulty patch of mine. :-( On Mon, Jun 20, 2016 at 7:08 PM, Juan Hernández <jhernand@redhat.com> wrote:
On 06/20/2016 06:02 PM, Yevgeny Zaspitsky wrote:
Hi All,
It looks like since [1] commit was merged to master the [2] became stale as it refers to findbugs-general maven profile that doesn't exist anymore.
Infra team, please update [2] asap, as it faulty marks all patches as -1.
[1] https://gerrit.ovirt.org/#/c/48687 [2] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_gerrit
Regards, Yevgeny
The fact that the job uses a profile that doesn't exist shouldn't be problematic, it will just cause a warning. It would be good to remove that "-Pfindbugs-general" option anynow, to avoid the warning.
I see the job running correctly for many patches. Do you have an example of a patch where it voted -1 incorrectly?
-- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
participants (2)
-
Juan Hernández -
Yevgeny Zaspitsky