All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Geissler <geissonator@gmail.com>
To: Lakshminarayana R Kammath <lkammath@in.ibm.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: [OpenBMC]: Unit test coverage analysis on openbmc repositories
Date: Wed, 4 Mar 2020 12:43:42 -0600	[thread overview]
Message-ID: <EDA605F3-6630-49FC-9244-0A2499138CFC@gmail.com> (raw)
In-Reply-To: <OFBAC0E531.E7E68FE5-ON0025851C.0053A4C8-0025851C.0055AA1E@notes.na.collabserv.com>



> On Feb 28, 2020, at 9:35 AM, Lakshminarayana R Kammath <lkammath@in.ibm.com> wrote:
> 
> Hi All,
>  
> Recently we worked on pulling the UT coverage analysis from all the available OpenBMC repositories
>  
> https://github.com/openbmc/openbmc-build-scripts/commit/229b76a95f87af60c976a0c0dfe84716c9ce5318
>  
> This script does following
> 	• Clone the repo
> 	• Use the CI build environment to build code
> 	• Publish the result in the following format
> Feedback's , views highly appreciated

Good stuff. I added this to a jenkins job which will run each day.

https://openpower.xyz/job/openbmc-unit-test-coverage/

You can then look at coverage info for your repo of interest by
clicking through the artifacts and getting to your coverage info.

For example:
https://openpower.xyz/job/openbmc-unit-test-coverage/lastSuccessfulBuild/artifact/openbmc-build-scripts/scripts/unit-test-meta-data/pldm/build/meson-logs/coveragereport/index.html 

The job uses the following to know which repositories to check so feel
free to throw up some commits if there are missing or invalid repos:
https://github.com/openbmc/openbmc-build-scripts/blob/master/scripts/repositories.txt

>  
> Thanks & Regards,
> Lakshminarayana Kamath
> --------------------------------------------------------------------------------------------------
> Senior Engineer,
> IBM India Software Labs
> Bangalore
> github:lkammath
> ---------------------------------------------------------------------------------------------------
>  
> 

  parent reply	other threads:[~2020-03-04 18:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 15:35 [OpenBMC]: Unit test coverage analysis on openbmc repositories Lakshminarayana R Kammath
2020-02-28 16:18 ` Brad Bishop
2020-02-28 16:30 ` Lakshminarayana R Kammath
2020-02-28 16:31   ` Brad Bishop
2020-02-28 16:36     ` Brad Bishop
2020-03-04  6:42       ` Lakshminarayana R Kammath
2020-02-28 16:39     ` Lakshminarayana R Kammath
2020-02-28 18:12       ` Nancy Yuen
2020-02-28 18:20 ` Patrick Venture
2020-03-05  1:25   ` James Feist
2020-03-03  4:48 ` Andrew Jeffery
2020-03-03  6:16   ` Lakshminarayana R Kammath
2020-03-05  7:57   ` Lakshminarayana R Kammath
2020-03-06  9:27     ` Lei YU
2020-03-04 18:43 ` Andrew Geissler [this message]
2020-02-28 16:08 lakshminarayan kamath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EDA605F3-6630-49FC-9244-0A2499138CFC@gmail.com \
    --to=geissonator@gmail.com \
    --cc=lkammath@in.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.