From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Fabian Stelzer <fs@gigacodes.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Adam Dinwoodie <adam@dinwoodie.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/2] test-lib: show missing prereq summary
Date: Mon, 15 Nov 2021 18:44:14 +0100 [thread overview]
Message-ID: <211115.865ysts45o.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <20211115160750.1208940-2-fs@gigacodes.de>
On Mon, Nov 15 2021, Fabian Stelzer wrote:
> When running the full test suite many tests can be skipped because of
> missing prerequisites. It not easy right now to get an overview of which
> ones are missing.
> When switching to a new machine or environment some libraries and tools
> might be missing or maybe a dependency broke completely. In this case
> the tests would indicate nothing since all dependant tests are simply
> skipped. This could hide broken behaviour or missing features in the
> build. Therefore this patch summarizes the missing prereqs at the end of
> the test run making it easier to spot such cases.
>
> - Add failed prereqs to the test results.
> - Aggregate and then show them with the totals.
>
> Signed-off-by: Fabian Stelzer <fs@gigacodes.de>
> ---
> t/aggregate-results.sh | 17 +++++++++++++++++
> t/test-lib.sh | 11 +++++++++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/t/aggregate-results.sh b/t/aggregate-results.sh
> index 7913e206ed..87c16fcee1 100755
> --- a/t/aggregate-results.sh
> +++ b/t/aggregate-results.sh
> @@ -6,6 +6,7 @@ success=0
> failed=0
> broken=0
> total=0
> +missing_prereq=
>
> while read file
> do
> @@ -30,10 +31,26 @@ do
> broken=$(($broken + $value)) ;;
> total)
> total=$(($total + $value)) ;;
> + missing_prereq)
> + missing_prereq="$missing_prereq,$value" ;;
> esac
> done <"$file"
> done
>
> +if test -n "$missing_prereq"
> +then
> + unique_missing_prereq=$(
> + echo $missing_prereq |
> + tr -s "," "\n" |
> + grep -v '^$' |
> + sort -u |
> + paste -s -d ',')
What is paste? Some out-of-tree debugging utility?
I think you might find a better way to do this shown in my
"ab/generate-command-list" topic, currently in seen. It removed most of
the same sort of tr|grep|sort etc. chain in generate-cmdlist.sh.
next prev parent reply other threads:[~2021-11-16 1:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:07 [PATCH 0/2] test-lib: improve missing prereq handling Fabian Stelzer
2021-11-15 16:07 ` [PATCH 1/2] test-lib: show missing prereq summary Fabian Stelzer
2021-11-15 17:44 ` Ævar Arnfjörð Bjarmason [this message]
2021-11-15 17:53 ` Junio C Hamano
2021-11-15 19:56 ` Fabian Stelzer
2021-11-15 22:10 ` Junio C Hamano
2021-11-16 14:19 ` Fabian Stelzer
2021-11-17 8:19 ` Junio C Hamano
2021-11-17 9:05 ` Fabian Stelzer
2021-11-15 16:07 ` [PATCH 2/2] test-lib: introduce required prereq for test runs Fabian Stelzer
2021-11-16 6:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=211115.865ysts45o.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=adam@dinwoodie.org \
--cc=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 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 NNTP newsgroup(s).