git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 code

From
Luke Diamand <luke@diamand.org>
Date
Mar 13, 2018, 14:45 UTC
Message-ID
<CAE5ih78HdDvN+x94H3Tzygis8QGROUe4B-yBubFH4simN2u9vQ@mail.gmail.com>
In-Reply-To
<20180313033643.7686-1-viethtran1620@gmail.com>
On 13 March 2018 at 03:36, Viet Hung Tran <viethtran1620@gmail.com> wrote:
Show 17 quoted lines
> Hello Mr. Schneider,
>
> Here is my link for the passed CI build I tested on my fork:
> https://travis-ci.org/VietHTran/git/builds/352103333
>
> In order to test .travis.yml configuration alone, I used a sample python
> script call "test.py" that is already successfully tested on my computer
> instead of using the git-p4.py like in the patch I submitted since the
> git-p4.py file still reports a lot of errors when running pylint.
>
> It is possible to fix all the git-p4.py errors. However, I think it would
> be best to fix each error separately with multiple commits (each should
> fix a specific problem such as indentication, variable naming, etc.)
> since there are a lot of changes needed to be made in the codes. Since the
> microproject requires that I submit one patch, I decided to submit a patch
> that includes changes in .travis.yml only. If you like, I can also submit the
> patches addressing changes on the git-p4.py that fix the pylint errors.

You can turn down the amount of messages it spews out, at which point it actually becomes quite useful.

I had a quick go with the list of enabled checkers found here:
   https://github.com/ClusterHQ/flocker/blob/master/.pylintrc

and it then gives about 40 warnings, all of which look like they could do with fixing.

I think fixing them in a few patches would be OK, rather than submitting 40 separate patches.

Quite a lot of the warnings are about the use of "file" - I've got a change I'm working on which fixes some of those already.

Luke
Show 34 quoted lines
>
> Thank you for feedback,
>
> Viet
>
> Signed-off-by: Viet Hung Tran <viethtran1620@gmail.com>
> ---
>  .travis.yml | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index 5f5ee4f3b..581d75319 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -46,6 +46,16 @@ matrix:
>          - docker
>        before_install:
>        script: ci/run-linux32-docker.sh
> +    - env: jobname=Pylint
> +      compiler:
> +      addons:
> +        apt:
> +          packages:
> +          - python
> +      before_install:
> +      install: pip install --user pylint
> +      script: pylint git-p4.py
> +      after_failure:
>      - env: jobname=StaticAnalysis
>        os: linux
>        compiler:
> --
> 2.16.2.440.gc6284da
>
Previous: Viet Hung TranNext: Viet Hung Tran
Message 5 of 8 in “git-ci: use pylint to analyze the git-p4 code”
  1. git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 12, 2018
  2. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 12, 2018
  3. Lars SchneiderMar 12, 2018
  4. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 13, 2018
  5. Luke DiamandMar 13, 2018
  6. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 14, 2018
  7. [GSoC][PATCH 1/2] git-ci: add .pylintrc fileViet Hung Tran, Mar 14, 2018
  8. [GSoC][PATCH 2/2] git-ci: update .pylintrc to ignore current warningViet Hung Tran, Mar 14, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.