From: Victoria Dye <vdye@github.com>
To: Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] ci(github): also skip logs of broken test cases
Date: Mon, 22 Jan 2024 14:41:41 -0800 [thread overview]
Message-ID: <dbe25fff-e1d4-41f2-8f8f-c538e8c2a77e@github.com> (raw)
In-Reply-To: <pull.1649.git.git.1705808313306.gitgitgadget@gmail.com>
Philippe Blain via GitGitGadget wrote:
> From: Philippe Blain <levraiphilippeblain@gmail.com>
>
> When a test fails in the GitHub Actions CI pipeline, we mark it up using
> special GitHub syntax so it stands out when looking at the run log. We
> also mark up "fixed" test cases, and skip passing tests since we want to
> concentrate on the failures.
>
> The finalize_test_case_output function in
> test-lib-github-workflow-markup.sh which performs this markup is however
> missing a fourth case: "broken" tests, i.e. tests using
> 'test_expect_failure' to document a known bug. This leads to these
> "broken" tests appearing along with any failed tests, potentially
> confusing the reader who might not be aware that "broken" is the status
> for 'test_expect_failure' tests that indeed failed, and wondering what
> their commits "broke".
>
> Also skip these "broken" tests so that only failures and fixed tests
> stand out.
>
> Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
> ---
> ci(github): also skip logs of broken test cases
>
> * An example of a run with failed tests appearing along with several
> "broken" tests:
> https://github.com/phil-blain/git/actions/runs/7589303055/job/20673657755
> * An example of a run with the same failures, but with this patch on
> top (no "broken" tests listed):
> * https://github.com/phil-blain/git/actions/runs/7598605434/job/20694762480
Thanks for making this change, the more focused logs are much nicer to read
(and ostensibly a bit more performant as well).
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1649%2Fphil-blain%2Fgithub-ci-skip-broken-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1649/phil-blain/github-ci-skip-broken-v1
> Pull-Request: https://github.com/git/git/pull/1649
>
> t/test-lib-github-workflow-markup.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/t/test-lib-github-workflow-markup.sh b/t/test-lib-github-workflow-markup.sh
> index 970c6538cba..33405c90d74 100644
> --- a/t/test-lib-github-workflow-markup.sh
> +++ b/t/test-lib-github-workflow-markup.sh
> @@ -42,8 +42,8 @@ finalize_test_case_output () {
> fixed)
> echo >>$github_markup_output "::notice::fixed: $this_test.$test_count $1"
> ;;
> - ok)
> - # Exit without printing the "ok" tests
> + ok|broken)
> + # Exit without printing the "ok" or ""broken" tests
And the implementation itself is nice and simple. Looks good to me!
> return
> ;;
> esac
>
> base-commit: e02ecfcc534e2021aae29077a958dd11c3897e4c
next prev parent reply other threads:[~2024-01-22 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 3:38 [PATCH] ci(github): also skip logs of broken test cases Philippe Blain via GitGitGadget
2024-01-22 22:41 ` Victoria Dye [this message]
2024-01-22 23:16 ` 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=dbe25fff-e1d4-41f2-8f8f-c538e8c2a77e@github.com \
--to=vdye@github.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=levraiphilippeblain@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 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).