Copy build artifacts for all test.py tests, so they show up in
artifacts storage for later inspection. The test.py tests output
in CI is basically useless, but it is far more useful in the html
output for analysis and debugging.
Reviewed-by: Simon Glass <s...@chromium.org>
Reviewed-by: Tom Rini <tr...@konsulko.com>
Suggested-by: Simon Glass <s...@chromium.org>
Signed-off-by: Marek Vasut <marek.vasut+rene...@mailbox.org>
---
Cc: Simon Glass <s...@chromium.org>
Cc: Tom Rini <tr...@konsulko.com>
---
V2: - Drop bogus comment
- Add RB from Tom and Simon
V3: - Add when:always to always collect artifacts, even in case of failure
- Move artifact copy into after_script
---
.gitlab-ci.yml | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 52d31a0e4ff..bd4ab576d56 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -30,6 +30,7 @@ stages:
fi
after_script:
+ - cp -v /tmp/${TEST_PY_BD}/*.{html,css} .
- rm -rf /tmp/uboot-test-hooks /tmp/venv
script:
# If we've been asked to use clang only do one configuration.
@@ -76,10 +77,12 @@ stages:
./test/py/test.py -ra --bd ${TEST_PY_BD} ${TEST_PY_ID}
${TEST_PY_TEST_SPEC:+"-k ${TEST_PY_TEST_SPEC}"}
--build-dir "$UBOOT_TRAVIS_BUILD_DIR"
- # It seems that the files in /tmp go away, so copy out what we need
- - if [[ "${TEST_PY_BD}" == "coreboot" ]]; then
- cp -v /tmp/coreboot/*.{html,css} .;
- fi
+ artifacts:
+ when: always
+ paths:
+ - "*.html"
+ - "*.css"
+ expire_in: 1 week
build all 32bit ARM platforms:
stage: world build
@@ -471,9 +474,4 @@ coreboot test.py:
TEST_PY_BD: "coreboot"
TEST_PY_TEST_SPEC: "not sleep"
TEST_PY_ID: "--id qemu"
- artifacts:
- paths:
- - "*.html"
- - "*.css"
- expire_in: 1 week
<<: *buildman_and_testpy_dfn
--
2.39.2
