From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci(github): bring back the 'print test failures' step
Date: Wed, 08 Jun 2022 16:14:22 -0700 [thread overview]
Message-ID: <xmqqtu8uoii9.fsf@gitster.g> (raw)
In-Reply-To: <pull.1252.git.1654684998599.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Wed, 08 Jun 2022 10:43:18 +0000")
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> Git now shows better information in the GitHub workflow runs when a test
> case failed. However, when a test case was implemented incorrectly and
> therefore does not even run, nothing is shown.
>
> Let's bring back the step that prints the full logs of the failed tests,
> and to improve the user experience, print out an informational message
> for readers so that they do not have to know/remember where to see the
> full logs.
Makes quite a lot of sense. Not all test gotchas are caught by
test-lint locally, and something like this would still be needed.
Will queue.
next prev parent reply other threads:[~2022-06-08 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 10:43 [PATCH] ci(github): bring back the 'print test failures' step Johannes Schindelin via GitGitGadget
2022-06-08 23:14 ` Junio C Hamano [this message]
2022-06-09 13:06 ` Ævar Arnfjörð Bjarmason
2022-06-10 16:40 ` Junio C Hamano
2022-06-10 17:32 ` Ævar Arnfjörð Bjarmason
2022-07-25 20:00 ` Ævar Arnfjörð Bjarmason
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=xmqqtu8uoii9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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).