test: fix possibly-undefined and deprecated call sites

[jd]

Two more error codes mypy leaves off under strict, both with real hits
in the test suite.

possibly-undefined: test_retry_state bound retry_state only inside
an except ExtractCallState block, then used it unconditionally. Had the
retry stopped raising, the test would have failed with NameError instead
of a useful assertion. Use assertRaises as a context manager, which both
asserts the exception is raised and binds the state unconditionally.

deprecated: asyncio.iscoroutinefunction is deprecated since 3.14 and
removed in 3.16, and was emitting a DeprecationWarning on every test run.
The line right below it already asserts the same property via
inspect.iscoroutinefunction, which is the documented replacement, so drop
the deprecated call rather than pin the suite to an API that is going away.

[jd]

This pull request is part of a Mergify stack:

#	Pull Request	Link
1	test: fix possibly-undefined and deprecated call sites	#681	👈
2	refactor: mark overridden methods with @OverRide	#682

[jd]

Revision history

#	Type	Changes	Reason	Date
1	initial	cdd9c7b		2026-08-05 15:39 UTC
2	rebase	cdd9c7b → dbf3491 (rebase only)		2026-08-05 15:39 UTC
3	rebase	dbf3491 → dc1546e (rebase only)		2026-08-05 15:47 UTC
4	rebase	dc1546e → d245e46 (rebase only)		2026-08-05 15:59 UTC

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-05 15:41 UTC · Rule: default · triggered by rule autoqueue
• ✅ Checks skipped · PR is already up-to-date
• 🚫 Left the queue — 2026-08-05 15:43 UTC · at dbf34914f7a03dd889480012dbf17b1a48e7f858

This pull request spent 1 minute 59 seconds in the queue, including 10 seconds running CI.

Waiting for

• depends-on=jd/tenacity#679 [⛓️ refactor: drop always-true truthiness checks and enable truthy-bool #679 [stack]]
• depends-on=jd/tenacity#680 [⛓️ refactor: declare BaseAction's REPR_FIELDS and NAME as ClassVar #680 [stack]]

All conditions

• depends-on=jd/tenacity#679 [⛓️ refactor: drop always-true truthiness checks and enable truthy-bool #679 [stack]]
  • test: fix possibly-undefined and deprecated call sites #681
• depends-on=jd/tenacity#680 [⛓️ refactor: declare BaseAction's REPR_FIELDS and NAME as ClassVar #680 [stack]]
  • test: fix possibly-undefined and deprecated call sites #681
• github-review-approved [🛡 GitHub branch protection]
  • test: fix possibly-undefined and deprecated call sites #681

Reason

Pull request #681 has been dequeued

Queue conditions are not satisfied:

• depends-on=jd/tenacity#679 [⛓️ refactor: drop always-true truthiness checks and enable truthy-bool #679 [stack]]
• depends-on=jd/tenacity#680 [⛓️ refactor: declare BaseAction's REPR_FIELDS and NAME as ClassVar #680 [stack]]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-05 15:48 UTC · Rule: default · triggered by rule autoqueue
• 🟠 Checks running · on draft merge queue: checking main (e6ef84a), #680 and #681 together #691
• 🚫 Left the queue — 2026-08-05 15:49 UTC · at dc1546e37b5ab1c97171fd10ed8d1e284168f11c

This pull request spent 1 minute 8 seconds in the queue, including 16 seconds running CI.

Required conditions to merge

• depends-on = jd/tenacity#680 [⛓️ refactor: declare BaseAction's REPR_FIELDS and NAME as ClassVar #680]
  • test: fix possibly-undefined and deprecated call sites #681
• github-review-approved [🛡 GitHub branch protection]
  • test: fix possibly-undefined and deprecated call sites #681

Reason

Pull request #681 has been dequeued

GitHub refused to merge the pull request. Pull Request has merge conflicts. This is usually enforced by a branch protection or ruleset rule.

Failing checks:

• 🟠 test (3.10, check) (job log)

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-05 16:00 UTC · Rule: default · triggered by rule autoqueue
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-08-05 16:00 UTC · at d245e46bf76ddbab0a6d92ede12b35f93bdd7ea8 · squash

This pull request spent 11 seconds in the queue, including 1 second running CI.

Required conditions to merge

• github-review-approved [🛡 GitHub branch protection]
  • test: fix possibly-undefined and deprecated call sites #681