From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Philippe Blain" <levraiphilippeblain@gmail.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: [PATCH v2] ci: run `make sparse` as part of the GitHub workflow
Date: Wed, 14 Jul 2021 11:50:33 +0000 [thread overview]
Message-ID: <pull.994.v2.git.1626263433838.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.994.git.1626177086682.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>
Occasionally we receive reviews after patches were integrated, where
`sparse` (https://sparse.docs.kernel.org/en/latest/ has more information
on that project) identified problems such as file-local variables or
functions being declared as global.
By running `sparse` as part of our Continuous Integration, we can catch
such things much earlier. Even better: developers who activated GitHub
Actions on their forks can catch such issues before even sending their
patches to the Git mailing list.
This addresses https://github.com/gitgitgadget/git/issues/345
Note: Not even Ubuntu 20.04 ships with a new enough version of `sparse`
to accommodate Git's needs. The symptom looks like this:
add-interactive.c:537:51: error: Using plain integer as NULL pointer
To counter that, we download and install the custom-built `sparse`
package from the Azure Pipeline that we specifically created to address
this issue.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
ci: run make sparse as a GitHub workflow
One of the earliest open source static analyzers is called "sparse", and
occasionally Ramsay Jones sends out mails on the Git mailing list that
some function or other should be declared static because sparse found
out that it is only used within the same file.
Let's add a GitHub workflow running "make sparse".
Example run:
https://github.com/gitgitgadget/git/pull/994/checks?check_run_id=3065255116
Changes since v1:
* The job was folded into main.yml
* The commit message and a code comment now explain why we have to
download & install a custom sparse package instead of using Ubuntu's
default one
* The commit message now contains a link to the documentation of the
sparse tool
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-994%2Fdscho%2Fci-enable-sparse-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-994/dscho/ci-enable-sparse-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/994
Range-diff vs v1:
1: d1af618dd73 ! 1: 8b631acfaa2 ci: run `make sparse` as a GitHub workflow
@@ Metadata
Author: Johannes Schindelin <Johannes.Schindelin@gmx.de>
## Commit message ##
- ci: run `make sparse` as a GitHub workflow
+ ci: run `make sparse` as part of the GitHub workflow
Occasionally we receive reviews after patches were integrated, where
- `sparse` identified problems such as file-local variables or functions
- being declared as global.
+ `sparse` (https://sparse.docs.kernel.org/en/latest/ has more information
+ on that project) identified problems such as file-local variables or
+ functions being declared as global.
By running `sparse` as part of our Continuous Integration, we can catch
such things much earlier. Even better: developers who activated GitHub
@@ Commit message
This addresses https://github.com/gitgitgadget/git/issues/345
+ Note: Not even Ubuntu 20.04 ships with a new enough version of `sparse`
+ to accommodate Git's needs. The symptom looks like this:
+
+ add-interactive.c:537:51: error: Using plain integer as NULL pointer
+
+ To counter that, we download and install the custom-built `sparse`
+ package from the Azure Pipeline that we specifically created to address
+ this issue.
+
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
- ## .github/workflows/run-sparse.yml (new) ##
-@@
-+name: Run `sparse`
-+
-+on: [push, pull_request]
-+
-+jobs:
+ ## .github/workflows/main.yml ##
+@@ .github/workflows/main.yml: jobs:
+ - uses: actions/checkout@v1
+ - run: ci/install-dependencies.sh
+ - run: ci/run-static-analysis.sh
+ sparse:
++ needs: ci-config
++ if: needs.ci-config.outputs.enabled == 'yes'
++ env:
++ jobname: sparse
+ runs-on: ubuntu-20.04
+ steps:
-+ - name: Download the `sparse` package
++ - name: Download a current `sparse` package
++ # Ubuntu's `sparse` version is too old for us
+ uses: git-for-windows/get-azure-pipelines-artifact@v0
+ with:
+ repository: git/git
+ definitionId: 10
+ artifact: sparse-20.04
-+ - name: Install the `sparse` package
++ - name: Install the current `sparse` package
+ run: sudo dpkg -i sparse-20.04/sparse_*.deb
-+ - name: Install a couple of dependencies
++ - name: Install other dependencies
+ run: |
+ sudo apt-get install -q -y libssl-dev libcurl4-openssl-dev libexpat-dev gettext zlib1g-dev
+ - uses: actions/checkout@v2
-+ - name: make sparse
-+ run: make sparse
- \ No newline at end of file
++ - run: make sparse
+ documentation:
+ needs: ci-config
+ if: needs.ci-config.outputs.enabled == 'yes'
.github/workflows/main.yml | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 73856bafc9d..1b5c0392079 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -350,6 +350,27 @@ jobs:
- uses: actions/checkout@v1
- run: ci/install-dependencies.sh
- run: ci/run-static-analysis.sh
+ sparse:
+ needs: ci-config
+ if: needs.ci-config.outputs.enabled == 'yes'
+ env:
+ jobname: sparse
+ runs-on: ubuntu-20.04
+ steps:
+ - name: Download a current `sparse` package
+ # Ubuntu's `sparse` version is too old for us
+ uses: git-for-windows/get-azure-pipelines-artifact@v0
+ with:
+ repository: git/git
+ definitionId: 10
+ artifact: sparse-20.04
+ - name: Install the current `sparse` package
+ run: sudo dpkg -i sparse-20.04/sparse_*.deb
+ - name: Install other dependencies
+ run: |
+ sudo apt-get install -q -y libssl-dev libcurl4-openssl-dev libexpat-dev gettext zlib1g-dev
+ - uses: actions/checkout@v2
+ - run: make sparse
documentation:
needs: ci-config
if: needs.ci-config.outputs.enabled == 'yes'
base-commit: 75ae10bc75336db031ee58d13c5037b929235912
--
gitgitgadget
next prev parent reply other threads:[~2021-07-14 11:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 11:51 [PATCH] ci: run `make sparse` as a GitHub workflow Johannes Schindelin via GitGitGadget
2021-07-13 16:55 ` Đoàn Trần Công Danh
2021-07-14 9:12 ` Johannes Schindelin
2021-07-13 17:34 ` Philippe Blain
2021-07-14 9:09 ` Johannes Schindelin
2021-07-14 10:13 ` Johannes Schindelin
2021-07-16 1:37 ` Ramsay Jones
2021-07-13 22:41 ` Junio C Hamano
2021-07-14 10:09 ` Johannes Schindelin
2021-07-14 16:00 ` Junio C Hamano
2021-07-14 20:54 ` Johannes Schindelin
2021-07-14 20:56 ` Junio C Hamano
2021-07-14 22:03 ` Johannes Schindelin
2021-07-14 22:27 ` Junio C Hamano
2021-07-16 15:25 ` Johannes Schindelin
2021-07-16 16:42 ` Junio C Hamano
2021-07-14 11:50 ` Johannes Schindelin via GitGitGadget [this message]
2021-07-26 17:53 ` [PATCH] ci: run "apt-get update" before "apt-get install" Jeff King
2021-07-26 18:22 ` Jeff King
2021-07-26 22:12 ` Junio C Hamano
2021-07-26 20:27 ` [PATCH v3] ci: run `make sparse` as part of the GitHub workflow Johannes Schindelin via GitGitGadget
2021-07-26 22:20 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.994.v2.git.1626263433838.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=levraiphilippeblain@gmail.com \
--cc=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).