mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-21 04:54:17 +02:00
Fix flaky timing test on Windows CI
Increase performance test threshold from 100ms to 1.0s. Windows CI runners are slower than Linux, and the 100ms threshold was too tight. The test's intent is to catch obvious regressions (e.g., accidentally re-introducing code generation), not to precisely benchmark. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
33a69d7d0a
commit
ee6f469aa5
1 changed files with 4 additions and 2 deletions
|
|
@ -731,9 +731,11 @@ class TestOpenAPIComprehensive:
|
|||
|
||||
end_time = time.time()
|
||||
|
||||
# Should be very fast (no code generation)
|
||||
# Should be fast (no code generation). Use generous threshold for slow
|
||||
# CI runners (Windows); the intent is to catch obvious regressions
|
||||
# (e.g., accidentally re-introducing code generation), not to benchmark.
|
||||
initialization_time = end_time - start_time
|
||||
assert initialization_time < 0.1 # Should be under 100ms
|
||||
assert initialization_time < 1.0
|
||||
|
||||
# Verify provider was created correctly
|
||||
assert provider is not None
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue