Skip to content

Bump pytest from 5.2.0 to 6.2.4 #760

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

Merged
merged 1 commit into from
Jun 19, 2021
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 25, 2021

Bumps pytest from 5.2.0 to 6.2.4.

Release notes

Sourced from pytest's releases.

6.2.4

pytest 6.2.4 (2021-05-04)

Bug Fixes

  • #8539: Fixed assertion rewriting on Python 3.10.

6.2.3

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.

6.2.2

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.

6.2.1

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.

... (truncated)

Commits

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 the dependencies Pull requests that update a dependency file label May 25, 2021
@joshmoore
Copy link
Member

Coverage.py warning: No data was collected. (no-data-collected)
============================= test session starts ==============================
platform linux -- Python 3.6.9, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: /home/runner/work/zarr-python/zarr-python, configfile: pytest.ini
plugins: cov-2.7.1, doctestplus-0.4.0
collected 0 items / 1 error

Another py36 issue?

@dependabot dependabot bot force-pushed the dependabot/pip/pytest-6.2.4 branch 3 times, most recently from 469a0e3 to 5af0985 Compare June 1, 2021 19:38
@dependabot dependabot bot force-pushed the dependabot/pip/pytest-6.2.4 branch from 5af0985 to eddf978 Compare June 16, 2021 18:26
@joshmoore
Copy link
Member

Note sure what's going on here.

@dependabot dependabot bot force-pushed the dependabot/pip/pytest-6.2.4 branch 3 times, most recently from d2d33e6 to 2e567d9 Compare June 18, 2021 05:45
@joshmoore
Copy link
Member

If anyone has an idea about this failure, I'm all 👂🏽 :

=========================== short test summary info ============================
ERROR 

@dependabot dependabot bot force-pushed the dependabot/pip/pytest-6.2.4 branch 2 times, most recently from f5c7c3a to b80203d Compare June 18, 2021 15:34
Bumps [pytest](https://github.com/pytest-dev/pytest) from 5.2.0 to 6.2.4.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@5.2.0...6.2.4)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/pip/pytest-6.2.4 branch from b80203d to 9abb9d4 Compare June 18, 2021 15:40
@joshmoore
Copy link
Member

Looks like something else that got merged fixed this. whew

@joshmoore joshmoore merged commit 1c3ebe5 into master Jun 19, 2021
@joshmoore joshmoore deleted the dependabot/pip/pytest-6.2.4 branch June 19, 2021 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant