Bump coverage from 5.3 to 6.3.1

[dependabot]

Bumps coverage from 5.3 to 6.3.1.

Release notes

Sourced from coverage's releases.

coverage-5.6b1

• Third-party packages are now ignored in coverage reporting. This solves a few problems:
  • Coverage will no longer report about other people’s code (issue 876). This is true even when using --source=. with a venv in the current directory.
  • Coverage will no longer generate “Already imported a file that will be measured” warnings about coverage itself (issue 905).
• The HTML report uses j/k to move up and down among the highlighted chunks of code. They used to highlight the current chunk, but 5.0 broke that behavior. Now the highlighting is working again.
• The JSON report now includes percent_covered_display, a string with the total percentage, rounded to the same number of decimal places as the other reports’ totals.

coverage-5.5

• coverage combine has a new option, --keep to keep the original data files after combining them. The default is still to delete the files after they have been combined. This was requested in issue 1108 and implemented in pull request 1110. Thanks, Éric Larivière.
• When reporting missing branches in coverage report, branches aren’t reported that jump to missing lines. This adds to the long-standing behavior of not reporting branches from missing lines. Now branches are only reported if both the source and destination lines are executed. Closes both issue 1065 and issue 955.
• Minor improvements to the HTML report:
  • The state of the line visibility selector buttons is saved in local storage so you don’t have to fiddle with them so often, fixing issue 1123.
  • It has a little more room for line numbers so that 4-digit numbers work well, fixing issue 1124.
• Improved the error message when combining line and branch data, so that users will be more likely to understand what’s happening, closing issue 803.

coverage-5.4

• The text report produced by coverage report now always outputs a TOTAL line, even if only one Python file is reported. This makes regex parsing of the output easier. Thanks, Judson Neer. This had been requested a number of times (issue 1086, issue 922, issue 732).
• The skip_covered and skip_empty settings in the configuration file can now be specified in the [html] section, so that text reports and HTML reports can use separate settings. The HTML report will still use the [report] settings if there isn’t a value in the [html] section. Closes issue 1090.
• Combining files on Windows across drives now works properly, fixing issue 577. Thanks, Valentin Lab.
• Fix an obscure warning from deep in the _decimal module, as reported in issue 1084.
• Update to support Python 3.10 alphas in progress, including PEP 626: Precise line numbers for debugging and other tools.

coverage-5.3.1

• When using --source on a large source tree, v5.x was slower than previous versions. This performance regression is now fixed, closing issue 1037.
• Mysterious SQLite errors can happen on PyPy, as reported in issue 1010. An immediate retry seems to fix the problem, although it is an unsatisfying solution.
• The HTML report now saves the sort order in a more widely supported way, fixing issue 986. Thanks, Sebastián Ramírez (pull request 1066).
• The HTML report pages now have a Sleepy Snake favicon.
• Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).
• Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

Changelog

Sourced from coverage's changelog.

Version 6.3.1 — 2022-02-01

• Fix: deadlocks could occur when terminating processes. Some of these deadlocks (described in issue 1310_) are now fixed.

• Fix: a signal handler was being set from multiple threads, causing an error: "ValueError: signal only works in main thread". This is now fixed, closing issue 1312_.

• Fix: --precision on the command-line was being ignored while considering --fail-under. This is now fixed, thanks to Marcelo Trylesinski <pull 1317_>_.

• Fix: releases no longer provide 3.11.0-alpha wheels. Coverage.py uses CPython internal fields which are moving during the alpha phase. Fixes issue 1316_.

.. _issue 1310: nedbat/coveragepy#1310 .. _issue 1312: nedbat/coveragepy#1312 .. _issue 1316: nedbat/coveragepy#1316 .. _pull 1317: nedbat/coveragepy#1317

.. _changes_63:

Version 6.3 — 2022-01-25

• Feature: Added the lcov command to generate reports in LCOV format. Thanks, Bradley Burns <pull 1289_>. Closes issues 587 <issue 587_> and 626 <issue 626_>_.

• Feature: the coverage data file can now be specified on the command line with the --data-file option in any command that reads or writes data. This is in addition to the existing COVERAGE_FILE environment variable. Closes issue 624. Thanks, Nikita Bloshchanevich <pull 1304_>.

• Feature: coverage measurement data will now be written when a SIGTERM signal is received by the process. This includes :meth:Process.terminate <python:multiprocessing.Process.terminate>, and other ways to terminate a process. Currently this is only on Linux and Mac; Windows is not supported. Fixes issue 1307_.

• Dropped support for Python 3.6, which reached end-of-life on 2021-12-23.

• Updated Python 3.11 support to 3.11.0a4, fixing issue 1294_.

• Fix: the coverage data file is now created in a more robust way, to avoid problems when multiple processes are trying to write data at once. Fixes issues 1303 <issue 1303_>_ and 883 <issue 883_>_.

... (truncated)

Commits

• 2551a2b build: prep for 6.3.1
• 2227d00 docs: a changelog entry for #1310, and misc cleanups
• d246788 docs: a changelog entry for #1317
• e8b4120 test: update --precision & --fail-under tests to really test the fix from #1317
• 73bb553 fix: use --precision argument when checking --fail-under (#1317)
• aad5ece build: don't provide pre-release wheels. #1316
• 87331de build: windows 3.11.0a4 started failing to save the pip cache
• d35e8c4 debug: better tracing of pytracer changed
• ea71ae9 fix: use a re-entrant lock to avoid self-deadlocking #1310
• e6a8102 test: skip tests on py 3.11.0a4 that are failing in metacov
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #36.