Skip to content
Snippets Groups Projects
Commit 71a77c70 authored by Oleg Plakida's avatar Oleg Plakida Committed by GitHub
Browse files

Add flawky tests report (#13654)

parent 4be32b17
No related merge requests found
...@@ -16,7 +16,7 @@ dir = "target/nextest" ...@@ -16,7 +16,7 @@ dir = "target/nextest"
# * retries = 3 # * retries = 3
# * retries = { backoff = "fixed", count = 2, delay = "1s" } # * retries = { backoff = "fixed", count = 2, delay = "1s" }
# * retries = { backoff = "exponential", count = 10, delay = "1s", jitter = true, max-delay = "10s" } # * retries = { backoff = "exponential", count = 10, delay = "1s", jitter = true, max-delay = "10s" }
retries = 0 retries = 5
# The number of threads to run tests with. Supported values are either an integer or # The number of threads to run tests with. Supported values are either an integer or
# the string "num-cpus". Can be overridden through the `--test-threads` option. # the string "num-cpus". Can be overridden through the `--test-threads` option.
...@@ -89,12 +89,12 @@ leak-timeout = "100ms" ...@@ -89,12 +89,12 @@ leak-timeout = "100ms"
# Output a JUnit report into the given file inside 'store.dir/<profile-name>'. # Output a JUnit report into the given file inside 'store.dir/<profile-name>'.
# If unspecified, JUnit is not written out. # If unspecified, JUnit is not written out.
# path = "junit.xml" path = "junit.xml"
# The name of the top-level "report" element in JUnit report. If aggregating # The name of the top-level "report" element in JUnit report. If aggregating
# reports across different test runs, it may be useful to provide separate names # reports across different test runs, it may be useful to provide separate names
# for each report. # for each report.
report-name = "nextest-run" report-name = "substrate"
# Whether standard output and standard error for passing tests should be stored in the JUnit report. # Whether standard output and standard error for passing tests should be stored in the JUnit report.
# Output is stored in the <system-out> and <system-err> elements of the <testcase> element. # Output is stored in the <system-out> and <system-err> elements of the <testcase> element.
......
...@@ -228,6 +228,28 @@ test-linux-stable: ...@@ -228,6 +228,28 @@ test-linux-stable:
--partition count:${CI_NODE_INDEX}/${CI_NODE_TOTAL} --partition count:${CI_NODE_INDEX}/${CI_NODE_TOTAL}
# we need to update cache only from one job # we need to update cache only from one job
- if [ ${CI_NODE_INDEX} == 1 ]; then rusty-cachier cache upload; fi - if [ ${CI_NODE_INDEX} == 1 ]; then rusty-cachier cache upload; fi
artifacts:
when: always
paths:
- target/nextest/default/junit.xml
reports:
junit: target/nextest/default/junit.xml
test-linux-stable-upload-test-results:
stage: test
needs:
- job: test-linux-stable
artifacts: true
extends:
- .docker-env
- .test-refs
script:
- cat target/nextest/default/junit.xml | xq . > target/nextest/default/junit.json
- "curl -v -XPOST --http1.1
-u ${ELASTIC_USERNAME}:${ELASTIC_PASSWORD}
https://elasticsearch.parity-build.parity.io/unit-tests/_doc/${CI_JOB_ID}
-H 'Content-Type: application/json'
-d @target/nextest/default/junit.json"
test-frame-support: test-frame-support:
stage: test stage: test
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment