| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Also btw, I think some of these tests are duplicative.
|
| |
|
|
|
|
| |
to the def
|
|
|
|
|
|
|
|
|
|
|
| |
The old way, we made and deleted .pth file around each test. This
caused problems because pth files are written to a common location
shared by all test workers, so tests would fail because pth files were
being deleted as other workers were trying to use them.
Now we make the pth file once per session. There's still a chance that
a worker will be using a pth file just as another worker is ending and
removing it.
|
|
|
|
| |
Eight fewer sub-processes
|
|
|
|
|
| |
The old code expected a dict with int keys, but iterables are simpler, so get
rid of a lot of dict.fromkeys() nonsense.
|
|
|
|
|
| |
It didn't work because the os module is frozen on 3.11, so it gets no
measurement. Use -X to disable the frozen modules feature for the test.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The fix for CTracer is egregious and will need to be updated when there's a
supported way to do it.
The fullcoverage skip is noted in
https://github.com/nedbat/coveragepy/issues/1278
The raise_through_with skip is noted in
https://github.com/nedbat/coveragepy/issues/1270
|
| |
|
|
|
|
|
|
|
|
|
| |
Originally I used setup_test because something went wrong when I used setUp. I
wrote https://github.com/pytest-dev/pytest/issues/8424 about it. There they say
to use `-p no:nose` to disable nose interpretation.
But now I simply went back to setUp, and all seems well? Not sure what changed,
but using the expected name is better.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python 3.11 made a traceback look like this:
Traceback (most recent call last):
File "{path}", line 8, in <module>
print(sys.argv[1])
~~~~~~~~^^^
IndexError: list index out of range
We needed to not care if that tilde-caret line was present or not.
|
| |
|
| |
|
|
|
|
| |
and also replace some calls with just-plain re.search.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Update tox.ini to let us run against PyPy3.8
- Some 3.8 behavior is (apparently) only on CPython
- PyPy3.8 doesn't get along with virtualenv yet
(https://github.com/pypa/virtualenv/issues/2182), so use venv instead for our
virtualenv tests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fix find_writable_pth_directory() to expect the OSError from the open()
call. In general, this is what's going to happen if the file is not
writable. The current logic could only be triggered e.g. if the file
was writable but the underlying filesystem run out of space.
|
|
|
|
|
|
| |
The tests in test_process run the exception handling in execfile.py, but
only under coverage, so metacov can't see it. These smaller tests
exercise the code without coverage on top.
|
| |
|
| |
|
| |
|
|
|
|
| |
That was for Python 2, which we don't support anymore.
|
| |
|
|
|
|
|
| |
Yes, this is completely unimportant. Don't ask me why I bothered, I'm
not really sure.
|
|
|
|
|
|
|
|
|
| |
I was using pytest.__file__ as a directory, but in 5.3.2, pytest changed
to be a package, so that wasn't the site-packages directory anymore, and
our .pth file was written someplace useless.
Now we don't rely on the structure of pytest (why did we ever?), and it
works again.
|
| |
|
|
|
|
|
|
|
|
| |
Fixes a few unusual issues with reports:
- #580: HTML report generation fails on too long path
- #584: File collisions in coverage report html
- #1167: Remove leading underscore in coverage html
|
|
|
|
|
|
|
| |
Use the same rounding rules for the fail-under message that are used for totals
everywhere else, so that it won't say:
total of 100 is less than fail-under=100
|
| |
|
|
|
|
|
|
| |
This makes coverage warnings visible when running test suites under
pytest. But it also means some uninteresting warnings would show up in
our own test suite, so we had to catch or suppress those.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The check for coverage files inside the --source check disables our
metacoverage. Removing it means that coverage files will still not be
measured, but the reason will be given as "is third-party" rather than
"is part of coverage.py," which is a small price to pay.
|
|
|
|
|
|
| |
This finishes the last bit of #905
Also includes tighter logging of the reason for not tracing modules.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid measuring code located where third-party packages get installed.
We have to take care to measure --source code even if it is installed in
a third-party location.
This also fixes #905, coverage generating warnings about coverage being
imported when it will be measured.
https://github.com/nedbat/coveragepy/issues/876
https://github.com/nedbat/coveragepy/issues/905
|
|
|
|
|
|
| |
I thought I knew when this passed and when it failed. Now that our tests
are not TestCase's, pytest is enforcing the xfails. This passes locally
on Mac, but fails in CI on Mac. So skip it.
|
| |
|
| |
|
| |
|
| |
|