From 11efafb05bc2cd87e36eff47b04f29c1624006a2 Mon Sep 17 00:00:00 2001 From: Arseny Sher Date: Tue, 15 Jun 2021 15:57:42 +0300 Subject: [PATCH] Don't capture pytest output in CI. Otherwise it is hard to see what is going on until the testing is done. --- .circleci/config.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 3638343d07..c6b41ea7c1 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -210,7 +210,12 @@ jobs: # # The junit.xml file allows CircleCI to display more fine-grained test information # in its "Tests" tab in the results page. - pytest --junitxml=$TEST_OUTPUT/junit.xml --tb=short $TEST_SELECTION $EXTRA_PARAMS + # -s prevents pytest from capturing output, which helps to see + # what's going on if the test hangs + # --verbose prints name of each test (helpful when there are + # multiple tests in one file) + # -rA prints summary in the end + pytest --junitxml=$TEST_OUTPUT/junit.xml --tb=short -s --verbose -rA $TEST_SELECTION $EXTRA_PARAMS - run: # CircleCI artifacts are preserved one file at a time, so skipping # this step isn't a good idea. If you want to extract the