• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

SAP / flake8-tergeo / 15535786280 / 1
100%
main: 100%

Build:
DEFAULT BRANCH: main
Ran 09 Jun 2025 01:36PM UTC
Files 71
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 Jun 2025 01:31PM UTC coverage: 99.932%. Remained the same
15535786280.1

push

github

web-flow
Bump pytest from 8.3.5 to 8.4.0 (#106)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.5 to
8.4.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>8.4.0</h2>
<h1>pytest 8.4.0 (2025-06-02)</h1>
<h2>Removals and backward incompatible breaking changes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11372">#11372</a>:
Async tests will now fail, instead of warning+skipping, if you don't
have any suitable plugin installed.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12346">#12346</a>:
Tests will now fail, instead of raising a warning, if they return any
value other than None.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12874">#12874</a>:
We dropped support for Python 3.8 following its end of life
(2024-10-07).</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12960">#12960</a>:
Test functions containing a yield now cause an explicit error. They have
not been run since pytest 4.0, and were previously marked as an expected
failure and deprecation warning.</p>
<p>See <code>the docs &lt;yield tests
deprecated&gt;</code>{.interpreted-text role=&quot;ref&quot;} for more
information.</p>
</li>
</ul>
<h2>Deprecations (removal in next major release)</h2>
<ul>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10839">#10839</a>:
Requesting an asynchronous fixture without a
[pytest_fixture_setup]{.title-ref} hook that resolves it will now give a
DeprecationWarning. This most commonly happens if a sync test requests
an async fixture. This should have no effect on a majority of users with
async tests or fixtures using async pytest plugins, but may affect
non-standard hook setups or <code>autouse=True</code>. For guidance on
how to work around this warning see
<code>sync-test-async-fixture</c... (continued)

486 of 486 branches covered (100.0%)

Branch coverage included in aggregate %.

3939 of 3942 relevant lines covered (99.92%)

1.0 hits per line

Source Files on job 15535786280.1
  • Tree
  • List 71
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 15535786280
  • 6e835810 on github
  • Prev Job for on main (#15516833560.1)
  • Next Job for on main (#15577977360.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc