From: Mike Bayer Date: Sat, 9 Apr 2022 15:32:50 +0000 (-0400) Subject: simplify coverage config X-Git-Tag: rel_2_0_0b1~361 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fd052732604a0d03167978215f0077e60b75851d;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git simplify coverage config I *think* we don't need to tell .coverage to look in lib, it seems to be covering from whereever successfuly. not sure, but want to run on jenkins to see how it comes out. Change-Id: Ib74f427a5b09fcbeba0188dcf02dab27c329a8cd --- diff --git a/.coveragerc b/.coveragerc deleted file mode 100644 index 5d6c2bdc41..0000000000 --- a/.coveragerc +++ /dev/null @@ -1,5 +0,0 @@ -[run] -include=lib/sqlalchemy/* - -[report] -omit=lib/sqlalchemy/testing/* \ No newline at end of file diff --git a/tox.ini b/tox.ini index df7787db04..1b39215057 100644 --- a/tox.ini +++ b/tox.ini @@ -3,11 +3,6 @@ envlist = py [testenv] -# note that we have a .coveragerc file that points coverage specifically -# at ./lib/sqlalchemy, and *not* at the build that tox might create under .tox. -# See the notes below for setenv for more detail. -# also using --cov-append so that we can aggregate multiple runs together. -# Jenkins etc. need to call "coverage erase" externally. cov_args=--cov=sqlalchemy --cov-report term --cov-append --cov-report xml --exclude-tag memory-intensive --exclude-tag timing-intensive -k "not aaa_profiling" install_command=python -m pip install {env:TOX_PIP_OPTS:} {opts} {packages}