[CI] hermes-lemonade-server / lemonade-ready-windows failed on stx (windows)

[github-actions]

This issue was opened automatically by the Test Playbooks workflow after the test lemonade-ready-windows failed on the main branch.

Failure scope

• Playbook: hermes-lemonade-server
• Test id: lemonade-ready-windows
• Device: stx
• Operating system: windows
• Runner labels: self-hosted, Windows, stx
• Runner name: xsj-aimlab-stxp-03
• Commit: 54c5223bf0557a22cb8db53751a3044bc68ceb68
• Workflow run: https://github.com/amd/playbooks/actions/runs/34577600809

Hardware / OS to use to reproduce

Run the failing test on a machine that matches the runner labels above (OS = windows, device = stx). The repo's self-hosted runners already advertise these labels; if you reproduce locally, use the same OS family and the same AMD device class.

How to dispatch the same test from CI

Re-run only the failing playbook on the same matrix entry by triggering the workflow with the playbook id:

gh workflow run test-playbooks.yml --repo amd/playbooks -f playbook_id=hermes-lemonade-server

The workflow's matrix narrows down to this (device, platform) combination automatically based on the playbook's tested_platforms.

How to run just this test locally

python .github/scripts/run_playbook_tests.py --playbook hermes-lemonade-server --platform windows --device stx

The runner extracts test blocks from playbooks/*/hermes-lemonade-server/README.md (the failing block starts around line 279).

Failing test (verbatim from the README)

• Timeout: 300s

$health = $null
for ($i = 0; $i -lt 120; $i++) {
  $health = curl.exe -sf --max-time 2 http://127.0.0.1:13305/api/v1/health
  if ($health) { break }
  Start-Sleep -Seconds 1
}
if (-not $health) { throw "Lemonade server not ready on http://127.0.0.1:13305/api/v1/health" }
Write-Host "OK: Lemonade server is ready"

Result

• Exit code: -1
• Runner error: Test timed out after 300 seconds

---

This issue is opened and deduplicated by .github/scripts/create_failure_issues.py. Close it once the failure is fixed; subsequent failures with the same scope will reopen a fresh issue.