From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 82FABA0C47 for ; Wed, 11 Aug 2021 16:09:51 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 717AB410EC; Wed, 11 Aug 2021 16:09:51 +0200 (CEST) Received: from mail-oi1-f171.google.com (mail-oi1-f171.google.com [209.85.167.171]) by mails.dpdk.org (Postfix) with ESMTP id 467AC40C35 for ; Wed, 11 Aug 2021 16:09:50 +0200 (CEST) Received: by mail-oi1-f171.google.com with SMTP id o20so4680747oiw.12 for ; Wed, 11 Aug 2021 07:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jCdIj/UgywogWX44OzQUOPmcKvFobEBfE1AkqQHVdKE=; b=XMoMp9f+r9QwYfAaPHjR0zyyr+anT5cRMn7b8TkCrpa5aOObCmoC2uvrnl1hzQ2KyW oqEHQO6XLJH2B8awe0p8CPSBkZXAtRtoS2fv3TeXzHzr83VUIY1Gc28Jo1g+daWpHGam H/mGsnPmTlrvwvmFqyR6TQN2HL0Fjll4ZAU/I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jCdIj/UgywogWX44OzQUOPmcKvFobEBfE1AkqQHVdKE=; b=uJlZ2Wq5uKRyZafYk5U3R62i9bn9XylK0Z/HoBs3FHnICGt70JJuGZUyM5Au4L1mTv uUh+5GK3nLVwXtjZ4bou63zzatYg0hJC5wMNyookbEa6mzf5vj56z2+POJJsnvsR3F0/ KNMAOeJa0BUcou2MG56iW+zoDJLnjqFZCX05t+DmvDW/NPlijhRSSmX6gw16t9oxGMgd 62+m3Dz9F1wQPCgk0nM3zV+sVSFp301UlOH3jyfOCVCVMqDn6SQQyM/cl57JpIARchYD J0XFi+w4QiWk9dwTm8D3Z8yVZ0fFeSwRiZ1yFCOIhQoZpVkpL9yzTi3iDIr8Vy4jN1cn ikGA== X-Gm-Message-State: AOAM532JDBv6RMT1b8VQzYl4Y5LEgrCZZAL4DeCiMQuGa3Piw64HT2EU uQmhPY55m4dyXHguJDeySq/58/jnWxUNVamw5R7ZFA== X-Google-Smtp-Source: ABdhPJzu95GceW15a7e0ltRW69FTRA1hQ6Sl7Zk/gjzg8PsImqSwXIs9ut0zEeVtGsiDCKY6Pc45TVr6ctjwvQXTI4A= X-Received: by 2002:aca:c484:: with SMTP id u126mr7594077oif.35.1628690989579; Wed, 11 Aug 2021 07:09:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Owen Hilyard Date: Wed, 11 Aug 2021 10:09:13 -0400 Message-ID: To: dts@dpdk.org, ci@dpdk.org Cc: dpdklab , Honnappa.Nagarahalli@arm.com, Aaron Conole , "Tu, Lijuan" , =?UTF-8?Q?Juraj_Linke=C5=A1?= Content-Type: multipart/alternative; boundary="000000000000e216db05c9492b3f" Subject: Re: [dpdk-ci] Tooling for DTS X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --000000000000e216db05c9492b3f Content-Type: text/plain; charset="UTF-8" The DTS working group has decided to move forward with black and pylama as tooling for DTS CI. On Wed, Jul 28, 2021 at 4:44 PM Owen Hilyard wrote: > 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 > > > --000000000000e216db05c9492b3f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The DTS working group has decided to move forward=C2=A0wit= h black and pylama as tooling for DTS CI.=C2=A0

On Wed, Jul 28, 2021 at 4:44= PM Owen Hilyard <ohilyard@iol.u= nh.edu> wrote:
Hello everyone,

During the DTS wo= rking group meeting, we discussed that it would be useful to have some auto= mated tooling to help assist the maintainers. These tools must produce mach= ine-readable output. There are a few categories that we would like to inclu= de.

1. Formatter

The form= atter 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.

<= div>3. Misc Static Analysis

Any other static analy= sis tools that may be useful.

My personal recommen= dations:

1. black

Black h= as the ability to parse the file before and after formatting and diff the A= STs, to ensure that no semantic changes occurred=C2=A0during formatting. Th= is would probably be our safest bet since we can be confident that it won&#= 39;t break anything.=C2=A0

2. pylama
This tool runs a superset of the analyzers run by Flake8
<= div>
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.= =C2=A0

Owen Hilyard


<= /div>
--000000000000e216db05c9492b3f--