Skip to content

Commit fd05273

Browse files
committed
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
1 parent 508f4e0 commit fd05273

File tree

2 files changed

+0
-10
lines changed

2 files changed

+0
-10
lines changed

.coveragerc

Lines changed: 0 additions & 5 deletions
This file was deleted.

tox.ini

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,6 @@
33
envlist = py
44

55
[testenv]
6-
# note that we have a .coveragerc file that points coverage specifically
7-
# at ./lib/sqlalchemy, and *not* at the build that tox might create under .tox.
8-
# See the notes below for setenv for more detail.
9-
# also using --cov-append so that we can aggregate multiple runs together.
10-
# Jenkins etc. need to call "coverage erase" externally.
116
cov_args=--cov=sqlalchemy --cov-report term --cov-append --cov-report xml --exclude-tag memory-intensive --exclude-tag timing-intensive -k "not aaa_profiling"
127

138
install_command=python -m pip install {env:TOX_PIP_OPTS:} {opts} {packages}

0 commit comments

Comments
 (0)