@coder: Coder sandbox smoke test 4 #1

Merged

satish merged 1 commit from coder/35f92bc1 into main

2026-09-05 07:40:15 +00:00

satish commented

2026-09-05 07:39:13 +00:00

Owner

Still broken. I've hit a hard environment blocker and want to flag it clearly rather than fake completion.

What happened

I have all the file content ready, but I could not commit it or create a branch/PR, because the sandbox's shell is unavailable — every Bash invocation (mine and a fresh test subagent's) fails with:

No suitable shell found. Claude CLI requires a Posix shell environment.
Please ensure you have a valid shell installed and the SHELL environment variable set.

This isn't flaky — it failed identically across multiple retries, different commands, and a completely independent subagent. There's no git tool available outside of Bash, so git checkout -b, git add, git commit, etc. are all unreachable from here. This looks like an infrastructure problem with the sandbox provisioning (missing SHELL/POSIX shell), not something fixable from inside the session.

What I did do (file-level only, not committed)

In /workspace (an existing empty repo, currently on main, with a stray leftover branch coder/35f92bc1 from what looks like a prior attempt that likely hit this same issue):

index.html — the smoke-test payload: a bare HTML page with <h1>hello</h1>.
README.md — updated to explain the file's test-only purpose and how to open/run it.
test.html — a tiny, dependency-free browser test that fetches index.html and asserts the <h1> says "hello" (since there's no Node/CI runner available without a shell, this is a manually-opened check rather than an automated one).

These are written to disk but not staged, not committed, and not on a feature branch — they're sitting as uncommitted changes on main in the working tree.

What a human needs to do before this is usable

Confirm the sandbox's shell provisioning (SHELL env var / POSIX shell binary) — that's the actual root cause blocking the @coder pipeline test itself.
Once shell access works, someone (me, re-run, or manually) needs to: git checkout -b coder/initial-build, add the three files, commit, and open the PR — the normal flow I'd otherwise have done end-to-end in under a minute, per the spec.

I didn't want to report "PR opened" or "tests pass" when neither actually happened — that would defeat the entire purpose of this smoke test, which is to verify the pipeline is trustworthy. Happy to retry the git/branch/PR steps immediately once shell access is restored.

Still broken. I've hit a hard environment blocker and want to flag it clearly rather than fake completion. ## What happened I have all the file content ready, but I could not commit it or create a branch/PR, because **the sandbox's shell is unavailable** — every `Bash` invocation (mine and a fresh test subagent's) fails with: ``` No suitable shell found. Claude CLI requires a Posix shell environment. Please ensure you have a valid shell installed and the SHELL environment variable set. ``` This isn't flaky — it failed identically across multiple retries, different commands, and a completely independent subagent. There's no git tool available outside of `Bash`, so `git checkout -b`, `git add`, `git commit`, etc. are all unreachable from here. This looks like an infrastructure problem with the sandbox provisioning (missing `SHELL`/POSIX shell), not something fixable from inside the session. ## What I did do (file-level only, not committed) In `/workspace` (an existing empty repo, currently on `main`, with a stray leftover branch `coder/35f92bc1` from what looks like a prior attempt that likely hit this same issue): - **`index.html`** — the smoke-test payload: a bare HTML page with `<h1>hello</h1>`. - **`README.md`** — updated to explain the file's test-only purpose and how to open/run it. - **`test.html`** — a tiny, dependency-free browser test that fetches `index.html` and asserts the `<h1>` says "hello" (since there's no Node/CI runner available without a shell, this is a manually-opened check rather than an automated one). These are written to disk but **not staged, not committed, and not on a feature branch** — they're sitting as uncommitted changes on `main` in the working tree. ## What a human needs to do before this is usable 1. Confirm the sandbox's shell provisioning (`SHELL` env var / POSIX shell binary) — that's the actual root cause blocking the @coder pipeline test itself. 2. Once shell access works, someone (me, re-run, or manually) needs to: `git checkout -b coder/initial-build`, add the three files, commit, and open the PR — the normal flow I'd otherwise have done end-to-end in under a minute, per the spec. I didn't want to report "PR opened" or "tests pass" when neither actually happened — that would defeat the entire purpose of this smoke test, which is to verify the pipeline is trustworthy. Happy to retry the git/branch/PR steps immediately once shell access is restored.

satish added 1 commit

2026-09-05 07:39:13 +00:00