[CI] lemonade-getting-started / lemonade-chat-qwen-windows failed on halo (windows)

[github-actions]

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

Failure scope

• Playbook: lemonade-getting-started
• Test id: lemonade-chat-qwen-windows
• Device: halo
• Operating system: windows
• Runner labels: self-hosted, Windows, halo
• Runner name: xsj-aimlab-halo-0
• Commit: bba38dfe1f3535aed4bdc16add29c15340751e20
• Workflow run: https://github.com/amd/playbooks/actions/runs/25616636882

Hardware / OS to use to reproduce

Run the failing test on a machine that matches the runner labels above (OS = windows, device = halo). 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=lemonade-getting-started

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 lemonade-getting-started --platform windows --device halo

The runner extracts test blocks from playbooks/*/lemonade-getting-started/README.md (the failing block starts around line 117).

Failing test (verbatim from the README)

• Timeout: 1200s

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

# Now that the server is responding, check if model is downloaded in Lemonade(robust JSON parse)
$parsed = $modelsJson | ConvertFrom-Json
$entry  = $parsed.data | Where-Object { $_.id -eq "Qwen3.5-4B-GGUF" } | Select-Object -First 1
if (-not $entry) { throw "Model Qwen3.5-4B-GGUF is not present in Lemonade /api/v1/models." }
if (-not $entry.downloaded) { throw "Model Qwen3.5-4B-GGUF is present but not downloaded in Lemonade. Please download it." }
Write-Host "OK: Qwen3.5-4B-GGUF model is downloaded in Lemonade"

# Model chat test
$body = @{
  model = "Qwen3.5-4B-GGUF"
  messages = @(@{ role = "user"; content = "Reply with exactly: OK" })
  temperature = 0
  max_tokens = 500
} | ConvertTo-Json -Depth 5
$out = curl.exe -s --max-time 300 http://127.0.0.1:13305/api/v1/chat/completions -H "Content-Type: application/json" -d $body
if (-not $out) { throw "Empty response from Lemonade chat/completions" }
Write-Host "OK: Model Qwen3.5-4B-GGUF responded"

Result

• Exit code: 1

stderr (last lines)

Lemonade server not ready on http://127.0.0.1:13305
At line:8 char:25
+ ... delsJson) { throw "Lemonade server not ready on http://127.0.0.1:1330 ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Lemonade server...127.0.0.1:13305:String) [], RuntimeException
    + FullyQualifiedErrorId : Lemonade server not ready on http://127.0.0.1:13305
 

---

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.

[sreeram-11]

The Lemonade server was not running on the Windows Halo runner xsj-aimlab-halo-0. The issue was resolved after manually logging into the runner and starting the Lemonade server.