public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Felix Polyudov" <felixp@ami.com>
To: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
	"michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
	"pedro.falcato@gmail.com" <pedro.falcato@gmail.com>
Cc: Rebecca Cran <rebecca@bsdio.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-rfc] RFC v2: Static Analysis in edk2 CI
Date: Mon, 27 Jun 2022 17:07:52 +0000	[thread overview]
Message-ID: <BN0PR10MB49813C5548C6A43B1AE8B729DEB99@BN0PR10MB4981.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB49291BBC639B34909EE56DB1D2B49@CO1PR11MB4929.namprd11.prod.outlook.com>

Yes, we can run other analyzer; however, in case of CodeChecker we also need a server to upload the result to.

> -----Original Message-----
> From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Michael D
> Kinney via groups.io
> Sent: Thursday, June 23, 2022 9:30 PM
> To: rfc@edk2.groups.io; pedro.falcato@gmail.com; Felix Polyudov
> <Felixp@ami.com>; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Rebecca Cran <rebecca@bsdio.com>; edk2-devel-groups-io
> <devel@edk2.groups.io>
> Subject: [EXTERNAL] Re: [edk2-rfc] RFC v2: Static Analysis in edk2 CI
>
>
> **CAUTION: The e-mail below is from an external source. Please exercise
> caution before opening attachments, clicking links, or following guidance.**
>
> I have Coverity scan builds running in a GitHub Action and then uploaded to
> Coverity.
>
> We should be able to configure a GitHub Action to run other analyzers.
>
> Mike
>
> > -----Original Message-----
> > From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Pedro
> > Falcato
> > Sent: Tuesday, June 14, 2022 1:00 PM
> > To: rfc@edk2.groups.io; POLUDOV, FELIX <felixp@ami.com>
> > Cc: Rebecca Cran <rebecca@bsdio.com>; edk2-devel-groups-io
> > <devel@edk2.groups.io>
> > Subject: Re: [edk2-rfc] RFC v2: Static Analysis in edk2 CI
> >
> > (Re-adding devel@ since Felix dropped it)
> >
> > On Tue, Jun 14, 2022 at 8:59 PM Pedro Falcato
> > <pedro.falcato@gmail.com>
> > wrote:
> >
> > > Just want to note that if we want to go ahead with fuzzing (I
> > > detailed a possible plan to do so in the mailing list a month or so
> > > ago) we will definitely need somewhere to run fuzzing (even if it's Google's
> syzbot).
> > > Getting somewhere where we can run static analysis, fuzzing just
> > > makes sense IMO (hell, who knows, maybe even CI or something like
> > > Gerrit for mailing list-less code reviews).
> > >
> > > On Tue, Jun 14, 2022 at 7:43 PM Felix Polyudov via groups.io
> > > <felixp= ami.com@groups.io> wrote:
> > >
> > >> Yes, LLVM/CLANG Static Analyzer is another possibility. I've
> > >> mentioned it in the first version of the RFC.
> > >> CodeChecker
> > >>
> (https://codechecker.readthedocs.io/en/latest/) is an open source front-end
> for the scan-build and clang-tidy.
> > >> It simplifies analyzer configuration and provides web-based report
> > >> storage. However, it has to be hosted somewhere.
> > >> If somebody has an idea on how edk2 community can host the
> > >> CodeChecker, that's definitely an option to consider.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > --
> > > Pedro Falcato

-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.

      reply	other threads:[~2022-06-27 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BN0PR10MB49817DF57E4808C7B340A067DEAB9@BN0PR10MB4981.namprd10.prod.outlook.com>
2022-06-13 18:54 ` RFC v2: Static Analysis in edk2 CI Michael D Kinney
2022-06-13 21:54   ` [edk2-rfc] " Pedro Falcato
2022-06-13 22:59     ` Rebecca Cran
     [not found]       ` <30179.1655232215857794558@groups.io>
     [not found]         ` <CAKbZUD3Pc+AEcOFjNjjjsV5KwBVVGochh9k4ufd1VpbF_xasjQ@mail.gmail.com>
2022-06-14 20:00           ` Pedro Falcato
2022-06-24  1:29             ` Michael D Kinney
2022-06-27 17:07               ` Felix Polyudov [this message]

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-list 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=BN0PR10MB49813C5548C6A43B1AE8B729DEB99@BN0PR10MB4981.namprd10.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox