Test Failure Analysis

Summary: Two unrelated pre-existing test failures were triggered in CI — a JWT expiration race condition on Windows and subprocess-spawning tests timing out with lowest-direct dependencies. Neither failure is caused by this PR's changes (which only pin pydantic-monty<0.0.8).

Failure 1: Windows — test_verify_token_validates_expiration

Root Cause: The test creates a JWT with expires_in=1 second, then immediately calls verify_token expecting it to be valid. On slow Windows CI runners, the token expires before the "immediate" verification runs — the token is issued at exp=1773515519 and the Token expired debug log fires at the same second, indicating the 1-second window is too tight for Windows CI.

Suggested Solution: Increase expires_in from 1 to something like 3 in the test, and adjust the time.sleep to match (e.g. time.sleep(3.1)). This gives more room on slow runners while still testing expiration.

• File: tests/server/auth/test_jwt_issuer.py:167-179

Failure 2: Lowest-direct dependencies — test_multi_client_lifespan + test_multi_client_force_close

Root Cause: Both tests are decorated with @pytest.mark.timeout(5) on this branch, but they spawn two subprocess MCP servers which takes longer than 5s on slow CI with minimum dependency versions. These tests are already fixed on main — the timeout has been bumped to @pytest.mark.timeout(15) there.

Suggested Solution: Since this is a patch branch that diverged before the timeout fix, this failure is moot as the PR has merged.

• File: tests/test_mcp_config.py (lines ~358, ~418)

DEBUG    Issued access token for client=client-abc jti=token-id exp=1773515519
[03/14/26 19:11:59] DEBUG    Token expired
E               authlib.jose.errors.JoseError: Token has expired:
src\fastmcp\server\auth\jwt_issuer.py:227: JoseError

@pytest.mark.timeout(5)
async def test_multi_client_lifespan(tmp_path: Path):
    ...
E       Failed: Timeout (>5.0s) from pytest-timeout.
tests/test_mcp_config.py:58: Failed

🤖 Generated with Claude Code