From 46ff4307569f9af0136178b55ca80b61e53315ea Mon Sep 17 00:00:00 2001 From: Michael Hanke Date: Fri, 17 Feb 2023 09:16:47 +0100 Subject: [PATCH] Make gathering coverage stats and their submission a nice to have At least in terms of success or failure of a workflow. See inside for reasoning. --- .github/workflows/test_crippledfs.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/test_crippledfs.yml b/.github/workflows/test_crippledfs.yml index bbea2f7e..984c9db7 100644 --- a/.github/workflows/test_crippledfs.yml +++ b/.github/workflows/test_crippledfs.yml @@ -75,6 +75,10 @@ jobs: echo "<< mount ==" PATH=$PWD/../tools/coverage-bin:$PATH python -m pytest -s -v --doctest-modules --cov=datalad_next --pyargs datalad_next - name: Report coverage + # compiling coverage and its submission is none critical, the vast majority of PRs + # will not possible impact the chances to do this. All PRs specifically changing + # the coverage setup will have to look here anyways + continue-on-error: true run: | python -m coverage combine -a /tmp/.coverage-entrypoints-*; python -m coverage xml