Repository navigation
Run all samples on a Windows runner from Git Bash - #142
Draft
paolosalvatori wants to merge 10 commits into
Draft
paolosalvatori wants to merge 10 commits into
paolosalvatori wants to merge 10 commits into
Conversation
A manual run with the new windows input runs, instead of the Linux matrix, seven samples on windows-latest from Git Bash, with MSYS_NO_PATHCONV=1 set as the README asks Windows users to do: the samples whose scripts pass a Cosmos DB partition key, resource IDs, Front Door paths, or local files read by az, curl, jq, python and zip. The emulator is a Linux image and Docker on the Windows runner runs Windows containers, so the job starts Docker Engine inside an Ubuntu WSL 2 distribution, runs the emulator there, and reaches it from Windows over ports WSL forwards to localhost. lstk finds the running container by its name, so run-samples.sh drives each sample exactly as it does on Linux. Git Bash ships no zip, so a shim hands zip -r to the 7-Zip the runner image ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
This was referenced Oct 23, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
…ged one
Installing docker.io in the WSL distribution already starts a Docker daemon on the Unix socket alone, so the daemon the job started with TCP port 2375 exited at once ("process with PID 1063 is still running"), the readiness check passed against the packaged daemon, and the Windows docker CLI found nothing on the port.
The step now stops the packaged daemon (its systemd units, or its PID file without systemd), starts its own, and waits on the TCP endpoint.
The Docker Engine log step runs only once WSL is set up, since its wsl-bash shell does not exist before that.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 14:32 — with
GitHub Actions
Failure
The Windows job takes its matrix from the setup job, which on a manual run with the windows input selects every sample on amd64, the architecture of the Windows runner, and the Linux matrix stays out of that run. It now provides what the remaining samples need: Java for the Service Bus sample, the zip MSYS2 ships (the 7-Zip shim dropped zip's -x exclusions), psql from the PostgreSQL the image installs, and the Go sqlcmd release, pinned with its SHA-256. As in the Linux job, a failed sample is retried once on a fresh emulator. lstk 1.4.0 cannot register its Azure CLI cloud on Windows when the CLI sits under C:\\Program Files: cmd.exe cuts the command line that carries the cloud configuration's JSON at that space. A junction without spaces, first on the PATH, works around it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 15:01 — with
GitHub Actions
Failure
paolosalvatori
had a problem deploying
to
AZURE
October 23, 2026 15:01 — with
GitHub Actions
Failure
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
… sample runs it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Unhandled CRLF output from native Windows tools causes deterministic failures in sample comparisons and numeric checks.
2 open issues
What changed in this PR
Adds an on-demand Windows CI path to exercise the sample suite from Git Bash with MSYS_NO_PATHCONV=1, complementing the Windows compatibility changes in #141.
Changes:
- Adds a manual
windowsinput that selects the full amd64 sample matrix instead of Linux jobs. - Runs Docker Engine and the LocalStack emulator inside WSL 2, accessible from Windows tools.
- Installs sample prerequisites and adds retry handling and diagnostic logs.
| File | Description |
|---|---|
.github/workflows/run-samples.yml |
Adds Windows dispatch routing, WSL-backed emulator setup, tooling, sample execution and retries. |
Review effort: Balanced
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
…the README asks The README asks Windows users for set -o igncr and export SHELLOPTS. Exporting SHELLOPTS in a step would also hand the step's own -e and pipefail to the sample scripts, so the job turns the option on for every bash through BASH_ENV instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
With DNS tunneling, on by default, the containers of the Docker Engine in WSL could not reach the 10.255.255.254 resolver WSL configures, so their lookups timed out: the Docker Engine log held dozens of "failed to query external DNS server" errors, and the Container Apps runtime could not pull the sample's image (ImagePullBackOff). Without tunneling, WSL hands out the NAT device on the host as the DNS server, which containers reach too (https://learn.microsoft.com/windows/wsl/troubleshooting#common-issues). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Motivation
#141 asks Windows users of Git Bash and MSYS2 to export
MSYS_NO_PATHCONV=1and adapts the scripts to it, but the Samples CI runs only on Linux, so nothing checks that the samples work from Git Bash.This adds a Windows job that runs every sample there, on demand, as a reproduction of that setup.
It is stacked on #141 and will be retargeted to
mainonce that pull request merges.Fixes SMF-980
Changes
windowsinput of the manual run starts the newwindowsjob instead of the Linux matrix. The setup job then selects every sample, on amd64, the architecture of the Windows runner, whateverrun_modeandarchsay.windows-latestand uses Git Bash, the defaultbashshell of Windows runners, withMSYS_NO_PATHCONV=1set as the README asks.run-samples.shdrives each sample exactly as in the Linux job, and a failed sample is retried once on a fresh emulator, as there.Vampire/setup-wsl) and runs the emulator there withdocker run. The Windows docker CLI andlstkreach that engine throughDOCKER_HOST=tcp://127.0.0.1:2375, which WSL forwards to the runner's localhost. Installingdocker.ioalready starts a daemon on the Unix socket alone, so the job stops it and starts one that also listens on TCP, and waits on the TCP endpoint.set -o igncr), turned on for every bash throughBASH_ENV, since exportingSHELLOPTSin a step would hand the step's own-eandpipefailto the sample scripts.lstk1.4.0 cannot register its Azure CLI cloud on Windows when the CLI sits underC:\Program Files: it passes the cloud configuration's JSON toaz.cmd, andcmd.executs that command line at the space ('C:\Program' is not recognized). A junction without spaces, first on the PATH, works around it untillstkpasses the JSON another way.zipMSYS2 ships,psqlfrom the image's PostgreSQL, the Gosqlcmdrelease pinned with its SHA-256, and Java 25 for the Service Bus sample. A step prints their versions.Tests
actionlintwithshellcheckon the workflow and on each bash step, and the repository's pre-commit hooks (zizmor,gitleaks)...., and Maven'smvnlauncher needs the path conversion (both fixed in Run the scripts from Git Bash and MSYS2 on Windows #141); the Docker daemon the package started (fixed here); and thelstkcloud registration above (worked around here).Related
🤖 Generated with Claude Code
https://claude.ai/code/session_01DhZ2ojsEXd2SGMo7s9uiZh