codecov-commenter
commented
5 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 93.54%. Comparing base (
4441ab3) to head (45cf3a0).
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #442 +/- ## ======================================= Coverage 93.54% 93.54% ======================================= Files 9 9 Lines 914 914 Branches 177 177 ======================================= Hits 855 855 Misses 35 35 Partials 24 24 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
==0.23.6->==0.23.7Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.23.7`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.7): pytest-asyncio 0.23.7 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.6...v0.23.7) ### 0.23.7 (2024-05-19) - Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases [#817](https://togithub.com/pytest-dev/pytest-asyncio/pull/817) #### Known issues As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [#706](https://togithub.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.