From a0165b1beb1f6861971887aa688dc7d4652ddd41 Mon Sep 17 00:00:00 2001 From: Slawek Kaplonski Date: Tue, 2 Mar 2021 15:34:21 +0100 Subject: [PATCH] Ignore python warnings in the fullstack job If there is too much output produced to the stdout/stderr during the tests, stestr can hangs and job will then time out. To avoid that in fullstack job, this patch is doing the same what was already done for functional job as well - set PYTHONWARNINGS variable to "ignore" to ignore all warnings and not send them to stdout. All info really needed to debug tests is still in the tests' logs in specific directories. Change-Id: I080381cb8a88a27130ac21c0e27fc915e38bdedd (cherry picked from commit 14955f93f6841fc65b7d761f15cf2227f31042d8) --- tox.ini | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tox.ini b/tox.ini index 554670647e9..f717bcd5e37 100644 --- a/tox.ini +++ b/tox.ini @@ -91,6 +91,9 @@ setenv = {[testenv]setenv} # workaround for DB teardown lock contention (bug/1541742) OS_TEST_TIMEOUT={env:OS_TEST_TIMEOUT:600} OS_TEST_PATH=./neutron/tests/fullstack +# Because of issue with stestr and Python3, we need to avoid too much output +# to be produced during tests, so we will ignore python warnings here + PYTHONWARNINGS=ignore deps = {[testenv:functional]deps} commands =