public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
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
Date: Tue, 14 Jun 2022 21:00:01 +0100	[thread overview]
Message-ID: <CAKbZUD1iTdToiQWvUeLnuZ8_L1S4chrQkvB0cYAKKFTgG4b1QQ@mail.gmail.com> (raw)
In-Reply-To: <CAKbZUD3Pc+AEcOFjNjjjsV5KwBVVGochh9k4ufd1VpbF_xasjQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

(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
>


-- 
Pedro Falcato

[-- Attachment #2: Type: text/html, Size: 2069 bytes --]

  parent reply	other threads:[~2022-06-14 20:00 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 [this message]
2022-06-24  1:29             ` Michael D Kinney
2022-06-27 17:07               ` Felix Polyudov

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=CAKbZUD1iTdToiQWvUeLnuZ8_L1S4chrQkvB0cYAKKFTgG4b1QQ@mail.gmail.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