Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

build(deps-dev): bump coverage from 4.0.3 to 5.3.1 #40

Merged
merged 1 commit into from
Jan 24, 2021
Merged

build(deps-dev): bump coverage from 4.0.3 to 5.3.1 #40

merged 1 commit into from
Jan 24, 2021

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 20, 2021 •
edited
Loading

Bumps coverage from 4.0.3 to 5.3.1.

Release notes

Sourced from coverage's releases.

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.

coverage-5.3

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

coverage-5.2.1

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
  • The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

coverage-5.2

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
  • The --skip-empty option is now available for the XML report, closing issue 976.
  • The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
  • If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
  • TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
  • The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

coverage-5.1

coverage-5.0.4

  • If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
  • The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
  • Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
  • Updated Python 3.9 support to 3.9a4.
  • HTML reports couldn’t be sorted if localStorage wasn’t available. This is now fixed: sorting works even though the sorting setting isn’t retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.

coverage-5.0.3

  • A performance improvement in 5.0.2 didn’t work for test suites that changed directory before combining data, causing “Couldn’t use data file: no such table: meta” errors (issue 916). This is now fixed.
  • Coverage could fail to run your program with some form of “ModuleNotFound” or “ImportError” trying to import from the current directory. This would happen if coverage had been packaged into a zip file (for example, on Windows), or was found indirectly (for example, by pyenv-virtualenv). A number of different scenarios were described in issue 862 which is now fixed. Huge thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and George-Cristian Bîrzan for protracted debugging sessions.
  • Added the “premain” debug option.
  • Added SQLite compile-time options to the “debug sys” output.

coverage-5.0.2

  • Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (issue 890). A side effect is that debug information about the config files read now shows absolute paths to the files.
  • When running programs as modules (coverage run -m) with --source, some measured modules were imported before coverage starts. This resulted in unwanted warnings (“Already imported a file that will be measured”) and a reduction in coverage totals (issue 909). This is now fixed.
  • If no data was collected, an exception about “No data to report” could happen instead of a 0% report being created (issue 884). This is now fixed.
  • The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in issue 891. Now, those files will not be measured, since their data would not be recordable.
  • A new warning (“dynamic-conflict”) is issued if two mechanisms are trying to change the dynamic context. Closes issue 901.

... (truncated)

Changelog

Sourced from coverage's changelog.

Version 5.3.1 --- 2020-12-19

  • 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 :ref:Sleepy Snake <sleepy> favicon.

  • Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).

  • Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

.. _issue 986: nedbat/coveragepy#986 .. _issue 1037: nedbat/coveragepy#1037 .. _issue 1010: nedbat/coveragepy#1010 .. _pull request 1066: nedbat/coveragepy#1066

.. _changes_53:

Version 5.3 --- 2020-09-13

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268_.

  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011_. This is now fixed.

.. _issue 268: nedbat/coveragepy#268 .. _issue 1011: nedbat/coveragepy#1011

.. _changes_521:

Version 5.2.1 --- 2020-07-23

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009_). This is now fixed.

... (truncated)

Commits
  • e65df09 Fix one pylint snag
  • f1dc6cc Name kit artifacts
  • c377e65 Latest sample HTML report
  • 4ac95eb Prep for 5.3.1
  • 37285cb Add a docstring to satisfy pylint
  • aeba5e6 Mention new wheels
  • 29e3241 Add time-created info to download_gha_artifacts.py
  • 215996b Build PyPy wheels also
  • 2dfe9f1 Thanks, Sebastián Ramírez
  • b12a97e 🐛 Fix sorting order storage in JQuery unload event
  • Additional commits viewable in compare view

Dependabot compatibility score

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 dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jan 20, 2021
@github-actions
Copy link

Expected release notes (by @dependabot[bot])

fixes:
Rollout Common Template Changes (3b63c22)
Added support of semantic versioning (0abc2d4)

others (will not be included in Semantic-Release notes):
bump coverage from 4.0.3 to 5.3.1 (8f06834)
remove typo error (da50e25)
sync develop with main (d532a50)
sync for policy (47387b6)
1ca03f0 Deprecate splunk_env_indexer submodule
3fd12b9 Bump deps/build/addonfactory_test_matrix_splunk (#30)
4beaff5 Bump pytest-splunk-addon from 1.3.6 to 1.4.0 in /tests (#31)
5e7f880 Bump deps/apps/splunk_env_indexer from b40bb65 to ada106b (#21)
added comments in requirements file (477febf)
fixed dependency version (2888b63)
PR review comments (365132d)
resolved merge conflicts (672807b)
updated files to make it in sync with common template (d727ca4)
updated psa version (d604310)
updated psa version (09fd9fe)
updated pytest-ci.ini (99634ee)
added dockerfile-saucelabs (6c5d95a)
updated test_matrix submodule (26688f8)
added credentials file (0374745)
5ddd03c test : rename folder knowledge
remove submodule and add dependency in config.yml (4c6fe74)
added modinput submodule (bd4635c)
make compatible with common template (a727cfe)
45fb784 Bump pytest-splunk-addon from 1.3.2 to 1.3.6 in /tests (#16)
d4286aa Bump pytest-splunk-addon from 1.3.0 to 1.3.2 in /tests (#10)
0987576 sync for policy (#9)
cdb1fb9 sync for policy (#7)
4bb6e6d Bump deps/build/addonfactory_test_matrix_splunk (#6)

  • I hereby acknowledge these release notes are 🥙 AWESOME 🥙

Base automatically changed from develop to main January 20, 2021 11:52
@ryanfaircloth ryanfaircloth merged commit 1d0135d into main Jan 24, 2021
@ryanfaircloth ryanfaircloth deleted the dependabot/pip/develop/coverage-5.3.1 branch January 24, 2021 12:54
@github-actions github-actions bot mentioned this pull request Jan 24, 2021
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ryanfaircloth