Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[loop-generated] [optimization] Slow test: test_create_timmy_default_includes_mcp_tools takes 2.5s #159

New Issue
Closed
opened 2026-03-15 15:08:44 +00:00 by hermes · 1 comment
hermes commented 2026-03-15 15:08:44 +00:00
Collaborator
Copy Link

Slowest unit test: tests/timmy/test_agent.py::test_create_timmy_default_includes_mcp_tools at 2.5s.

This test creates a Timmy agent with MCP tools. Likely bottleneck: MCP initialization, subprocess spawning, or heavy fixture setup.

Target: under 500ms. Profile and optimize — mock heavy I/O, lazy-load MCP, or restructure fixtures.

Also slow:

  • test_run_exhausts_retries (2.0s) — uses real sleep in retry loops
  • test_run_retries_on_transient_error (2.0s) — same
  • test_grok_chat_without_key (1.5s) — likely network timeout

These are unit tests. They should not have real I/O waits.

Slowest unit test: `tests/timmy/test_agent.py::test_create_timmy_default_includes_mcp_tools` at 2.5s. This test creates a Timmy agent with MCP tools. Likely bottleneck: MCP initialization, subprocess spawning, or heavy fixture setup. Target: under 500ms. Profile and optimize — mock heavy I/O, lazy-load MCP, or restructure fixtures. Also slow: - test_run_exhausts_retries (2.0s) — uses real sleep in retry loops - test_run_retries_on_transient_error (2.0s) — same - test_grok_chat_without_key (1.5s) — likely network timeout These are unit tests. They should not have real I/O waits.
hermes commented 2026-03-15 15:39:55 +00:00
Author
Collaborator
Copy Link

Triage Update — Current Slow Test Data (2026-03-15)

The issue title references test_create_timmy_default_includes_mcp_tools at 2.5s, but current profiling shows different bottlenecks:

31.84s  tests/timmy/test_introspection.py::TestRunSelfTests::test_returns_dict_with_expected_keys
12.79s  tests/e2e/test_ollama_integration.py::test_timmy_agent_with_available_model (e2e, expected)
 4.11s  tests/timmy/test_agent.py::test_create_timmy_includes_tools_for_large_model
 2.00s  tests/timmy/test_agent_retry.py::test_run_exhausts_retries (real sleep)
 2.00s  tests/timmy/test_agent_retry.py::test_run_retries_on_transient_error (real sleep)

The 31.8s introspection test now has its own issue. This issue should focus on:

  1. The retry tests using real time.sleep() — mock the sleep
  2. The 4.1s agent test — profile and optimize fixture setup

Updated target: all unit tests under 1s each (excluding e2e).

[triage-generated]

## Triage Update — Current Slow Test Data (2026-03-15) The issue title references `test_create_timmy_default_includes_mcp_tools` at 2.5s, but current profiling shows different bottlenecks: ``` 31.84s tests/timmy/test_introspection.py::TestRunSelfTests::test_returns_dict_with_expected_keys 12.79s tests/e2e/test_ollama_integration.py::test_timmy_agent_with_available_model (e2e, expected) 4.11s tests/timmy/test_agent.py::test_create_timmy_includes_tools_for_large_model 2.00s tests/timmy/test_agent_retry.py::test_run_exhausts_retries (real sleep) 2.00s tests/timmy/test_agent_retry.py::test_run_retries_on_transient_error (real sleep) ``` The 31.8s introspection test now has its own issue. This issue should focus on: 1. The retry tests using real `time.sleep()` — mock the sleep 2. The 4.1s agent test — profile and optimize fixture setup Updated target: all unit tests under 1s each (excluding e2e). [triage-generated]
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#159
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?