Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update coverage to 5.0.3 #6982

Merged
merged 1 commit into from Jan 12, 2020
Merged

Update coverage to 5.0.3 #6982

merged 1 commit into from Jan 12, 2020

Conversation

@pyup-bot
Copy link
Contributor

pyup-bot commented Jan 12, 2020

This PR updates coverage from 5.0.1 to 5.0.3.

Changelog

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.

.. _issue 862: https://github.com/nedbat/coveragepy/issues/862
.. _issue 916: https://github.com/nedbat/coveragepy/issues/916


.. _changes_502:

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`_.

- ``coverage run --debug=sys`` would fail with an AttributeError. This is now
fixed (`issue 907`_).

.. _issue 884: https://github.com/nedbat/coveragepy/issues/884
.. _issue 890: https://github.com/nedbat/coveragepy/issues/890
.. _issue 891: https://github.com/nedbat/coveragepy/issues/891
.. _issue 901: https://github.com/nedbat/coveragepy/issues/901
.. _issue 907: https://github.com/nedbat/coveragepy/issues/907
.. _issue 909: https://github.com/nedbat/coveragepy/issues/909


.. _changes_501:
Links
@vorpal-buildbot

This comment has been minimized.

Copy link
Contributor

vorpal-buildbot commented Jan 12, 2020

Changelogs

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.

.. _issue 862: nedbat/coveragepy#862
.. _issue 916: nedbat/coveragepy#916

.. _changes_502:

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_.

  • coverage run --debug=sys would fail with an AttributeError. This is now
    fixed (issue 907_).

.. _issue 884: nedbat/coveragepy#884
.. _issue 890: nedbat/coveragepy#890
.. _issue 891: nedbat/coveragepy#891
.. _issue 901: nedbat/coveragepy#901
.. _issue 907: nedbat/coveragepy#907
.. _issue 909: nedbat/coveragepy#909

.. _changes_501:

@codecov

This comment has been minimized.

Copy link

codecov bot commented Jan 12, 2020

Codecov Report

Merging #6982 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6982      +/-   ##
==========================================
- Coverage   45.79%   45.77%   -0.03%     
==========================================
  Files         272      272              
  Lines       13677    13677              
  Branches     2052     2052              
==========================================
- Hits         6264     6260       -4     
- Misses       7125     7128       +3     
- Partials      288      289       +1
Impacted Files Coverage Δ
magic/image_fetcher.py 35.66% <0%> (-3.19%) ⬇️
maintenance/elo.py 0% <0%> (ø) ⬆️
decksite/view.py 61.12% <0%> (ø) ⬆️
decksite/views/person_achievements.py 35% <0%> (ø) ⬆️
decksite/data/rule.py 23.42% <0%> (ø) ⬆️
decksite/league.py 34.76% <0%> (+0.33%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30a039b...11088e7. Read the comment docs.

@mergify mergify bot merged commit 4eb7ece into master Jan 12, 2020
7 checks passed
7 checks passed
Codacy/PR Quality Review Up to standards. A positive pull request.
Details
Summary 1 rule matches
Details
codecov/project 45.77% (-0.03%) compared to 30a039b
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
pdm/automerge Waiting for "merge when ready"
pyup.io/safety-ci No dependencies with known security vulnerabilities.
Details
@mergify mergify bot deleted the pyup-update-coverage-5.0.1-to-5.0.3 branch Jan 12, 2020
@vorpal-buildbot

This comment has been minimized.

Copy link
Contributor

vorpal-buildbot commented Jan 12, 2020

Seen on LOGS, PROD (created by @pyup-bot and merged by @mergify[bot] 19 seconds ago) Please check your changes!

@TravisBuddy

This comment has been minimized.

Copy link

TravisBuddy commented Jan 13, 2020

Hey @pyup-bot,
Your changes look good to me!

View build log

TravisBuddy Request Identifier: 6393b910-359b-11ea-ae1d-83bda137e929
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.