This issue was opened automatically by the Test Playbooks workflow after the test openclaw-sandbox-image-windows failed on the main branch.
Failure scope
- Playbook:
openclaw-lemonade-server
- Test id:
openclaw-sandbox-image-windows
- Device:
rx7900xt
- Operating system:
windows
- Runner labels:
self-hosted, Windows, rx7900xt
- Runner name:
CS-RORDMZ-DT136
- Commit:
60fb4cac864b0a4e8451b80518797f38b0c61ba0
- Workflow run: https://github.com/amd/playbooks/actions/runs/30252884496
Hardware / OS to use to reproduce
Run the failing test on a machine that matches the runner labels above (OS = windows, device = rx7900xt). 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=openclaw-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 openclaw-lemonade-server --platform windows --device rx7900xt
The runner extracts test blocks from playbooks/*/openclaw-lemonade-server/README.md (the failing block starts around line 781).
Failing test (verbatim from the README)
$ErrorActionPreference = "Stop"
$script = @'
set -euo pipefail
export PATH="/mnt/wsl/docker-desktop/cli-tools/usr/bin:$HOME/.npm-global/bin:$HOME/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH"
docker_config="$(mktemp -d)"
cleanup() {
rm -rf "$docker_config"
}
trap cleanup EXIT
export DOCKER_CONFIG="$docker_config"
printf '{ "auths": {} }\n' > "$DOCKER_CONFIG/config.json"
docker version
docker build -t openclaw-sandbox:bookworm-slim - <<'DOCKERFILE'
FROM debian:bookworm-slim
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y --no-install-recommends \
bash ca-certificates curl git jq python3 ripgrep \
&& rm -rf /var/lib/apt/lists/*
RUN useradd --create-home --shell /bin/bash sandbox
USER sandbox
WORKDIR /home/sandbox
CMD ["sleep", "infinity"]
DOCKERFILE
docker image inspect openclaw-sandbox:bookworm-slim >/dev/null
echo "OK: OpenClaw sandbox Docker image is available inside WSL"
'@
$script = $script -replace "`r`n", "`n"
$tmp = Join-Path $env:TEMP "openclaw-sandbox-image-windows.sh"
[System.IO.File]::WriteAllText($tmp, $script, [System.Text.UTF8Encoding]::new($false))
try {
$full = [System.IO.Path]::GetFullPath($tmp)
$drive = $full.Substring(0,1).ToLower()
$rest = $full.Substring(2).Replace('\','/')
$wslTmp = "/mnt/$drive$rest"
wsl -d Ubuntu-24.04 -- bash "$wslTmp"
if ($LASTEXITCODE -ne 0) { throw "OpenClaw sandbox image build failed inside WSL" }
}
finally {
Remove-Item $tmp -Force -ErrorAction SilentlyContinue
}
Result
stderr (last lines)
OpenClaw sandbox image build failed inside WSL
At line:47 char:30
+ ... ODE -ne 0) { throw "OpenClaw sandbox image build failed inside WSL" }
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (OpenClaw sandbo...iled inside WSL:String) [], RuntimeException
+ FullyQualifiedErrorId : OpenClaw sandbox image build failed inside WSL
stdout (last lines)
The command 'docker' could not be found in this WSL 2 distro.
We recommend to activate the WSL integration in Docker Desktop settings.
For details about using Docker Desktop with WSL 2, visit:
https://docs.docker.com/go/wsl2/
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.
This issue was opened automatically by the Test Playbooks workflow after the test
openclaw-sandbox-image-windowsfailed on themainbranch.Failure scope
openclaw-lemonade-serveropenclaw-sandbox-image-windowsrx7900xtwindowsself-hosted,Windows,rx7900xtCS-RORDMZ-DT13660fb4cac864b0a4e8451b80518797f38b0c61ba0Hardware / OS to use to reproduce
Run the failing test on a machine that matches the runner labels above (OS =
windows, device =rx7900xt). 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:
The workflow's matrix narrows down to this
(device, platform)combination automatically based on the playbook'stested_platforms.How to run just this test locally
The runner extracts test blocks from
playbooks/*/openclaw-lemonade-server/README.md(the failing block starts around line 781).Failing test (verbatim from the README)
1800sResult
1stderr (last lines)
stdout (last lines)
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.