Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Update dependency pytest to v6.2.5 #15

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pytest (source, changelog) 6.2.0 -> 6.2.5 age adoption passing confidence

Release Notes

pytest-dev/pytest (pytest)

v6.2.5

Compare Source

pytest 6.2.5 (2021-08-29)

Trivial/Internal Changes

  • #​8494: Python 3.10 is now supported.
  • #​9040: Enable compatibility with pluggy 1.0 or later.

v6.2.4

Compare Source

pytest 6.2.4 (2021-05-04)

Bug Fixes

  • #​8539: Fixed assertion rewriting on Python 3.10.

v6.2.3

Compare Source

pytest 6.2.3 (2021-04-03)

Bug Fixes

  • #​8414: pytest used to create directories under /tmp with world-readable
    permissions. This means that any user in the system was able to read
    information written by tests in temporary directories (such as those created by
    the tmp_path/tmpdir fixture). Now the directories are created with
    private permissions.

    pytest used silenty use a pre-existing /tmp/pytest-of-<username> directory,
    even if owned by another user. This means another user could pre-create such a
    directory and gain control of another user's temporary directory. Now such a
    condition results in an error.

v6.2.2

Compare Source

pytest 6.2.2 (2021-01-25)

Bug Fixes

  • #​8152: Fixed "(<Skipped instance>)" being shown as a skip reason in the verbose test summary line when the reason is empty.
  • #​8249: Fix the faulthandler plugin for occasions when running with twisted.logger and using pytest --capture=no.

v6.2.1

Compare Source

pytest 6.2.1 (2020-12-15)

Bug Fixes

  • #​7678: Fixed bug where ImportPathMismatchError would be raised for files compiled in
    the host and loaded later from an UNC mounted path (Windows).

  • #​8132: Fixed regression in approx: in 6.2.0 approx no longer raises
    TypeError when dealing with non-numeric types, falling back to normal comparison.
    Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
    and happened to compare correctly to a scalar if they had only one element.
    After 6.2.0, these types began failing, because they inherited neither from
    standard Python number hierarchy nor from numpy.ndarray.

    approx now converts arguments to numpy.ndarray if they expose the array
    protocol and are not scalars. This treats array-like objects like numpy arrays,
    regardless of size.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants