From: Anthony PERARD <[email protected]>
Patch series available in this git branch:
https://xenbits.xenproject.org/git-http/people/aperard/xen-unstable.git
br.ci-tools-tests-junit-fixes-v1
All the *-tools-tests-* are currently only checking automatically if the
machine as booted. The only way to find out if one of the tools/tests failed is
to read the console output by hand.
Also, tests-rangeset always return success even if there's a failure.
Fix all that, and add some improvement, and add SELECTED_JOBS_ONLY to
analyze.yaml
How it looks:
success:
https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/1850830262/test_report
failure:
https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/1850830637/test_report
Cheers,
Anthony PERARD (9):
CI: Add SELECTED_JOBS_ONLY to analyze.yaml
tools/tests: Fix return value of test-rangeset
CI: Fix status check for tools/tests
CI: Ignore run-tools-test return value
CI: Have the gitlab job fail on tools/tests failure
CI: Upload junit result as artefact
CI: Use CDATA avoid the need to escape tests outputs
CI: Workaround extra content in junit
CI: Add timing to junit
automation/gitlab-ci/analyze.yaml | 3 +++
automation/gitlab-ci/test.yaml | 1 +
automation/scripts/qubes-x86-64.sh | 18 ++++++++++++++++--
automation/scripts/run-tools-tests | 11 +++++++----
tools/tests/rangeset/test-rangeset.c | 2 +-
5 files changed, 28 insertions(+), 7 deletions(-)
--
Anthony PERARD
