From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Lars Schneider" <larsxschneider@gmail.com>,
"Derrick Stolee" <stolee@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: [PATCH 1/2] travis-ci: run Coccinelle static analysis with two parallel jobs
Date: Mon, 23 Jul 2018 15:02:29 +0200 [thread overview]
Message-ID: <20180723130230.22491-2-szeder.dev@gmail.com> (raw)
In-Reply-To: <20180723130230.22491-1-szeder.dev@gmail.com>
Currently the static analysis build job runs Coccinelle using a single
'make' job. Using two parallel jobs cuts down the build job's run
time from around 10-12mins to 6-7mins, sometimes even under 6mins
(there is quite large variation between build job runtimes). More
than two parallel jobs don't seem to bring further runtime benefits.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
---
ci/run-static-analysis.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ci/run-static-analysis.sh b/ci/run-static-analysis.sh
index fe4ee4e06b..fa719c9ef9 100755
--- a/ci/run-static-analysis.sh
+++ b/ci/run-static-analysis.sh
@@ -5,6 +5,6 @@
. ${0%/*}/lib-travisci.sh
-make coccicheck
+make --jobs=2 coccicheck
save_good_tree
--
2.18.0.408.g42635c01bc
next prev parent reply other threads:[~2018-07-23 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 13:02 [PATCH 0/2] travis-ci: fail if Coccinelle found something to transform SZEDER Gábor
2018-07-23 13:02 ` SZEDER Gábor [this message]
2018-07-23 13:02 ` [PATCH 2/2] travis-ci: fail if Coccinelle static analysis " SZEDER Gábor
2018-07-23 13:23 ` Derrick Stolee
2018-07-26 9:08 ` SZEDER Gábor
2018-07-26 16:49 ` Junio C Hamano
2018-07-23 13:06 ` [PATCH 3/2 for pb/bisect-helper-2] squash! bisect--helper: `bisect_start` shell function partially in C SZEDER Gábor
2018-07-23 13:24 ` Derrick Stolee
2018-07-23 13:25 ` [PATCH 0/2] travis-ci: fail if Coccinelle found something to transform Derrick Stolee
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=20180723130230.22491-2-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=pclouds@gmail.com \
--cc=stolee@gmail.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 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.