All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Additional linting in meta-layer repotest
Date: Wed, 3 Nov 2021 18:10:02 -0500	[thread overview]
Message-ID: <YYMWyuIBPaFNp8z9@heinlein> (raw)
In-Reply-To: <YXlpsDxZGsbvgHpQ@heinlein>

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

On Wed, Oct 27, 2021 at 10:01:04AM -0500, Patrick Williams wrote:
> Hello,
> 
> Ed recently added a test-phase called 'repotest'[1,2] in the openbmc/openbmc
> repository that allows us to perform sanity checking on commits at that level
> beyond a simple "does this compile".  The initial checking he added was to
> ensure that no new patches are added to the tree (in violation of our meta-layer
> coding guidelines).
> 
> I'm adding[3] additional capabilities to this script to enable linting in the
> repository.  This will run `shellcheck` for shell scripts and `eslint` for JSON
> (Some might be unaware that Manoj added JSON linting with `eslint` as part of
> our normal unit-test / formatting scripts[4] as well).  Once this is in place
> new commits will fail CI if they add new shellscripts that violate `shellcheck`
> rules or JSON with invalid parsing.
> 
> Currently, there is quite an extensive list of 'exempted' scripts (~100) which
> already fail `shellcheck` rules.  It is quite likely that some of these are
> real bugs, so I would strongly urge if you are the maintainer of one of the
> meta-layers holding an 'exempted' script that you look over the `shellcheck`
> failures.  Hopefully over the next few months we will greatly reduce the number
> of scripts in this exemption list by cleaning up the issues.
> 
> 1. https://lore.kernel.org/openbmc/CAH2-KxDe6hR1V-Lz1k8cdD11jEquy4UhR4LfLhg37E5EG42EJg@mail.gmail.com/
> 2. https://github.com/openbmc/openbmc/blob/master/meta-phosphor/scripts/run-repotest
> 3. https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/48349
> 4. https://github.com/openbmc/openbmc-build-scripts/blob/master/scripts/format-code.sh#L31
> -- 
> Patrick Williams

This is now merged.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-11-03 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 15:01 Additional linting in meta-layer repotest Patrick Williams
2021-11-03 23:10 ` Patrick Williams [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-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=YYMWyuIBPaFNp8z9@heinlein \
    --to=patrick@stwcx.xyz \
    --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.