DPDK CI discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org, ci@dpdk.org
Cc: dpdklab <dpdklab@iol.unh.edu>,
	Honnappa.Nagarahalli@arm.com, "Aaron Conole" <aconole@redhat.com>,
	"Tu, Lijuan" <lijuan.tu@intel.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-ci] Tooling for DTS
Date: Wed, 28 Jul 2021 16:44:29 -0400	[thread overview]
Message-ID: <CAHx6DYD10eZ4POhnUPrDh7Eag=GurXEVp-kM1TKA_fRjWgd+Kw@mail.gmail.com> (raw)

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

Hello everyone,

During the DTS working group meeting, we discussed that it would be useful
to have some automated tooling to help assist the maintainers. These tools
must produce machine-readable output. There are a few categories that we
would like to include.

1. Formatter

The formatter should be capable of a strict reformatting to PEP8.

2. Linter

We must be able to customize the output or suppress individual instances of
an issue.

3. Misc Static Analysis

Any other static analysis tools that may be useful.

My personal recommendations:

1. black

Black has the ability to parse the file before and after formatting and
diff the ASTs, to ensure that no semantic changes occurred during
formatting. This would probably be our safest bet since we can be confident
that it won't break anything.

2. pylama

This tool runs a superset of the analyzers run by Flake8

I'd like to start by getting a list of candidates, then we can narrow down
tools until we reach a final set of tools to run in CI for DTS.

Owen Hilyard

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

             reply	other threads:[~2021-07-28 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 20:44 Owen Hilyard [this message]
2021-08-11 14:09 ` Owen Hilyard

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='CAHx6DYD10eZ4POhnUPrDh7Eag=GurXEVp-kM1TKA_fRjWgd+Kw@mail.gmail.com' \
    --to=ohilyard@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=dts@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).