Browse Source

gci: Upload the junit.xml report

Can be used in a second stage to generate stats and detect flaky
tests.
master
Christian Decker 4 years ago
committed by Rusty Russell
parent
commit
bb15d7f042
  1. 9
      .github/workflows/ci.yaml

9
.github/workflows/ci.yaml

@ -184,7 +184,7 @@ jobs:
cat << 'EOF' > pytest.ini cat << 'EOF' > pytest.ini
[pytest] [pytest]
addopts=-p no:logging --color=yes --timeout=1800 --timeout-method=thread --test-group-random-seed=42 --force-flaky --no-success-flaky-report --max-runs=3 addopts=-p no:logging --color=yes --timeout=1800 --timeout-method=thread --test-group-random-seed=42 --force-flaky --no-success-flaky-report --max-runs=3 --junitxml=report.xml
markers = markers =
slow_test: marks tests as slow (deselect with '-m "not slow_test"') slow_test: marks tests as slow (deselect with '-m "not slow_test"')
EOF EOF
@ -245,3 +245,10 @@ jobs:
eatmydata make -j32 eatmydata make -j32
eatmydata $TEST_CMD eatmydata $TEST_CMD
fi fi
- name: Upload Unit Test Results
if: always()
uses: actions/upload-artifact@v2
with:
name: Junit Report ${{ github.run_number }}.${{ job.container.id }}
path: report.xml

Loading…
Cancel
Save