Ben,
In theory, there are statistics captured, but I have not investigated
how to utilize them.
Generally speaking, I'd prefer not to overload Jenkins
managing/displaying stats as a few of the plugins that we recently
removed were graph intensive and complete memory/cpu hogs. I'd prefer
to do offline processing of log data to generate reports rather than
have jenkins do the work. There are some ideas being tossed about on
that front, but no deliverables have been committed to at the present time.
Thanks,
-daw-
On 2/3/2021 3:20 AM, Benoit Ganne (bganne) wrote:
Very nice!
Do you also get statistics per failure cause?
Best
ben
-----Original Message-----
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Dave Wallace
Sent: mercredi 3 février 2021 02:28
To: vpp-dev <vpp-dev@lists.fd.io>
Subject: [vpp-dev] Jenkins/Gerrit Failure Cause Notifications
Folks,
Per a request by Dave Barach in the VPP Monthly Community Meeting, I
have added new rules to the VPP Failure Cause Management database [0] of
the Jenkins Build Analyzer plugin [1] to provide notifications in
gerrit/jenkins of build failure indications. The rules are applied to
the log of each Jenkins job which fails to identify the failure cause in
the build log.
You can preview the notifications in the gerrit change [2] which I have
been using to verify that the rules work correctly. You will see the
description of the build failure cause listed on the Gerrit notification
status line. The jenkins job status page will contain links in the
"Identified problems" section of the page for each rule.
Please note that in there is an issue with the reporting of multiple
instances of same failure contained in a build log (or maybe that is a
non-feature of the plugin). Presently only the 1st failure is listed in
the indications list on the jenkins build status page. In particular,
in the case of multiple 'make test' testcase failures [3], you will need
to search the log for any additional failures beyond one linked to in
the 'Indication 1' link [4].
I will continue to monitor job failures for viable failure signatures
that I can add to the . If you find a failure that you think is a good
candidate, then please directly email me the URL to the jenkins job
build status page along with the string to search for in the log and I
will add a new rule for it.
Thanks,
-daw-
[0] https://plugins.jenkins.io/build-failure-analyzer/
[1] https://jenkins.fd.io/view/vpp/failure-cause-management/
[2] https://gerrit.fd.io/r/c/vpp/+/31092
[3] https://jenkins.fd.io/job/vpp-verify-master-ubuntu1804-x86_64/2050/
[4]
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1804-
x86_64/2050/consoleFull#-14603433817be1b593-44ad-45a7-8ca6-701783403621
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18658): https://lists.fd.io/g/vpp-dev/message/18658
Mute This Topic: https://lists.fd.io/mt/80343945/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
