admin/mcp-nextcloud
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test(integration): bump Astrolabe search-input wait 10s->30s (nc32 UI flake)

Browse Source 
With the vector-sync gauge flake fixed, the plotly test now reaches the UI
phase. On a loaded nc32 CI runner the Astrolabe SPA can take >10s to mount its
search component, so `.mcp-search-input input` wasn't visible within the old
10s budget (playwright TimeoutError). Bump to 30s, matching the loading-
indicator wait just below. nc31 already rendered well within budget.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Chris Coutinho
2026-06-17 23:26:25 +02:00
co-authored by Claude Opus 4.8
parent a9e512d1dc
commit 650e60de57
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/integration/test_astrolabe_plotly_visualization.py
+5 -2
View File
@@ -246,9 +246,12 @@ The visualization should show this document as a point in PCA-reduced space.
await navigate_to_astrolabe_main(page)
# Fill search query - find the Astrolabe search input specifically
# The NcTextField component wraps the input in a div with class mcp-search-input
# The NcTextField component wraps the input in a div with class mcp-search-input.
# 30s (not 10s): the Astrolabe SPA can be slow to mount its search
# component on a loaded CI runner (observed on nc32) — matches the
# loading-indicator budget below.
search_input = page.locator(".mcp-search-input input")
await search_input.wait_for(timeout=10000, state="visible")
await search_input.wait_for(timeout=30000, state="visible")
await search_input.fill(unique_term)
logger.info("Entered search query: %s", unique_term)