Tweak Pytest logging in CI for less overwhelming logging of successful tests

.travis.yml

@@ -17,7 +17,6 @@ conditions: v1
 env:
   global:
     - PANTS_CONFIG_FILES="${TRAVIS_BUILD_DIR}/pants.travis-ci.ini"
-    - PYTEST_PASSTHRU_ARGS="-v --duration=3"
     - LC_ALL="en_US.UTF-8"
     # This tells the ./pants runner script to avoid trying to clean the workspace when changing
     # python versions. CI starts off without the .python-interpreter-constraints file, so it would otherwise

build-support/bin/ci.sh

@@ -104,6 +104,10 @@ esac
 # We're running against a Pants clone.
 export PANTS_DEV=1
 
+# We only want to output failures and skips.
+# See https://docs.pytest.org/en/latest/usage.html#detailed-summary-report.
+export PYTEST_PASSTHRU_ARGS="-q -rfa"
+
 # Determine the Python version to use for bootstrapping pants.pex. This would usually not be
 # necessary to set when developing locally, because the `./pants` and `./pants2` scripts set
 # these constraints for us already. However, we must set the values here because in

build-support/travis/travis.yml.mustache

@@ -10,7 +10,6 @@ conditions: v1
 env:
   global:
     - PANTS_CONFIG_FILES="${TRAVIS_BUILD_DIR}/pants.travis-ci.ini"
-    - PYTEST_PASSTHRU_ARGS="-v --duration=3"
     - LC_ALL="en_US.UTF-8"
     # This tells the ./pants runner script to avoid trying to clean the workspace when changing
     # python versions. CI starts off without the .python-interpreter-constraints file, so it would otherwise