----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Allon Mureinik" <amureini@redhat.com> Cc: "infra" <infra@ovirt.org>, "Juan Hernandez" <jhernand@redhat.com> Sent: Sunday, January 19, 2014 6:00:27 PM Subject: Re: no email alerts about animal-sniffer failrures
was missing the email trigger for failure. thanks for noticing. Thanks for fixing.
btw - should this be cloned for 3.4 as well? (currently on master)
probably not a bad idea, but if we're limited on resources, it's not a must.
----- Original Message -----
From: "Allon Mureinik" <amureini@redhat.com> To: "infra" <infra@ovirt.org> Cc: "Eyal Edri" <eedri@redhat.com>, "Juan Hernandez" <jhernand@redhat.com> Sent: Thursday, January 16, 2014 6:19:02 PM Subject: no email alerts about animal-sniffer failrures
Hi guys,
Earlier today, a patch was merged[1] that broke the JDK6 compliance that the GWT compilation relies on. (Specifically, this patch did not seem to actually harm anything, but that's beside the point here.)
Jenkin's animal-sniffer job failed on this patch[2] (which is fine - it's it job to fail), but looking at the output of the failure, no emails were sent out: --- Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default-cli) on project common: Signature errors found. Verify them and put @IgnoreJRERequirement on them. cause : Signature errors found. Verify them and put @IgnoreJRERequirement on them. Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default-cli) on project common: Signature errors found. Verify them and put @IgnoreJRERequirement on them. <stacktrace snipped> ... 30 more channel stopped No emails were triggered. Finished: FAILURE ---
Is this intentional? If not, can this be fixed?
[1] http://gerrit.ovirt.org/#/c/15596/ [2] http://jenkins.ovirt.org/job/ovirt_engine_animal_sniffer_check/5926/