fix(serve): call startServe with the signature bd-emv left it holding

The second semantic conflict from the bd-emv merge, and one git could not see.
bd-f3n added this file calling startServe(t, bd, p), where p is a
proxiedProject; bd-emv independently rewrote startServe to take the directory
and environment separately, so server mode could pass its own env. Neither
side touched the other's lines, so the merge was textually clean and produced
a test file that does not compile.

The bd-emv signature is the one that survives — it is the one three server-mode
call sites need — so the call site moves to it rather than the other way round.
This commit is contained in:
CI Bot 2026-07-31 18:39:29 +00:00
commit 1622598aef

View file

@ -60,7 +60,7 @@ func TestProxiedServerServeClaim(t *testing.T) {
t.Parallel()
bd := buildEmbeddedBD(t)
p := newSharedProxiedProject(t, bd, "srvcl")
sp := startServe(t, bd, p)
sp := startServe(t, bd, p.dir, bdProxiedEnv(p.dir))
t.Run("a claim over HTTP is the same claim the CLI sees", func(t *testing.T) {
issue := bdProxiedCreate(t, bd, p.dir, "claim over http", "-p", "1")