summaryrefslogtreecommitdiff
path: root/t/test-lib-github-workflow-markup.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2022-05-21 22:18:52 +0000
committerJunio C Hamano <gitster@pobox.com>2022-05-21 16:25:56 -0700
commit448de909a7dc0e0cc80aff6eff84de56a4c8bbfc (patch)
tree862467ec33219dde72ba7fdb084bf1f9a0ca04ca /t/test-lib-github-workflow-markup.sh
parent0f5ae593bea7314184608a32122da73ed559f219 (diff)
downloadgit-448de909a7dc0e0cc80aff6eff84de56a4c8bbfc.tar.gz
ci(github): skip the logs of the successful test cases
In most instances, looking at the log of failed test cases is enough to identify the problem. In some (rare?) instances, a previous test case that was marked as successful actually has information pertaining to a later test case that fails. To allow the page to load relatively quickly, let's only show the logs of the failed test cases to be shown. The full logs are available for download as artifacts, should a deeper investigation become necessary. Co-authored-by: Victoria Dye <vdye@github.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/test-lib-github-workflow-markup.sh')
-rw-r--r--t/test-lib-github-workflow-markup.sh4
1 files changed, 4 insertions, 0 deletions
diff --git a/t/test-lib-github-workflow-markup.sh b/t/test-lib-github-workflow-markup.sh
index d8dc969df4..1ef0fd5ba8 100644
--- a/t/test-lib-github-workflow-markup.sh
+++ b/t/test-lib-github-workflow-markup.sh
@@ -40,6 +40,10 @@ finalize_test_case_output () {
fixed)
echo >>$github_markup_output "::notice::fixed: $this_test.$test_count $1"
;;
+ ok)
+ # Exit without printing the "ok" tests
+ return
+ ;;
esac
echo >>$github_markup_output "::group::$test_case_result: $this_test.$test_count $*"
test-tool >>$github_markup_output path-utils skip-n-bytes \