Skip to content

test: run the serial backend group beside the other suites - #170

Merged
Phototonic merged 16 commits into
devfrom
test/faster-suites
Nov 18, 2026
Merged

Phototonic merged 16 commits into
devfrom
test/faster-suites

Conversation

@Phototonic

@Phototonic Phototonic commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

Makes the portable test run finish sooner, locally and in CI, without removing or relaxing a check. In CI the Linux step goes from about 305 s to about 150 to 230 s, and the Windows step from about 320 s to about 220 to 280 s (full Windows set: about 1020 s to about 780 s). No test is removed, and every pass and skip count is unchanged.

Measured causes, from recent CI runs and local per-file timings:

  • The serial backend group was about two thirds of the Linux step. The backend files that take Setup coordination ports run in one --test-concurrency=1 invocation (about 207 s of about 305 s), before the typechecks, the parallel backend group and the browser-model and automation tests. One file in it, managed-step-http.test.ts, is about 80 percent of it. It is latency-bound: one request after another, each starting a worker thread, plus a few deliberate deadline waits. It uses roughly one to two cores.
  • Every test process and worker thread recompiled the same modules.
  • The Windows job ran its two native files one after the other (about 190 to 220 s and about 150 to 160 s of tests).
  • Two Linux jobs always ran apt-get update and an install (7 to 29 s) for tools the image already has.

Changes:

  1. scripts/ci.ts runs the serial Setup-port group in one lane beside a second lane (both typechecks, the parallel backend group, the browser-model and automation tests). The serial group stays one --test-concurrency=1 invocation that nothing else joins. The other lane has its worker count capped at cores minus two and runs under nice, so the serial group's timing assertions keep their headroom. The second build comparison, the SDK check and the package checks still run after all tests.
  2. Port confinement, checked with a probe preloaded through NODE_OPTIONS that wraps net.Server.prototype.listen (it follows worker threads and child processes, including ones given a hand-built environment, so the bundled build/service/main.js is covered). Every non-serial step was run under it, with and without CP_BUILT_SERVICE=1 after build:all. Summary: no listen on a Setup port (25000 to 28999) from any of the 74 files in the parallel backend group or the browser and automation tests in the CI configuration; with CP_BUILT_SERVICE=1, one file, tests/backend/plan-cleanup-service.test.ts (its built-service restart test), takes writer slots (three service processes, two ports each), and the browser and automation tests still take none. That file is skipped in CI, but the plan now moves it into the serial group whenever CP_BUILT_SERVICE=1 is set (fencedWhenSet in scripts/ci-backend.ts), so no configuration puts a port-taking file beside the serial group. The probe was temporary and is not in the diff. My first probe, a source patch on the acquisition call, missed the bundled service; this one does not.
  3. New bun run test:fast (typechecks, parallel backend group, browser-model and automation tests; skips the serial port-bound group) and bun run test:all (everything portable CI tests except packaging and the rebuild comparison). Both share one plan (scripts/test-plan.ts, which takes a core count so one to three cores are tested) with CI. The runner (scripts/test-lanes.ts) is POSIX-first, with a best-effort Windows stop path I could not run: it prints each step's output whole (the last 2 MB if noisier), names running steps about every minute, and lists durations. The first failure, SIGINT, SIGTERM, SIGHUP or a closed output pipe stops every lane; a repeated signal or a step that has not stopped in 10 s is killed and abandoned even if a leftover process holds its pipes; every group it started is killed again when the steps settle and when the runner exits or crashes; an interrupted run exits 128 plus the signal number. A step it stopped is reported as stopped, one that fails by itself as failed with its output. On Windows steps are not detached and are stopped with taskkill /T /F (unit-tested for the command chosen, never run on Windows; the typecheck step's ./node_modules/.bin/tsc is a POSIX path). Documented in CONTRIBUTING.md.
  4. Node's compile cache (NODE_COMPILE_CACHE, under the ignored node_modules/.cache/) for every step. It is checked against each source's hash, so a changed file is recompiled. Each run starts from an empty cache, because entries are keyed by file name and the fixtures run from fresh temporary folders, so a kept cache grew about 30 MB a run. Alone, the heaviest managed-step test went from 9.0 s to 4.8 s. It did not change the typecheck times.
  5. The two Linux CI jobs install the ZIP tools only when the image lacks them (that step now takes 0 s).
  6. The Windows job starts windows-platform and windows-service as two processes at once, each in its own --test-concurrency=1 runner and as the same unprivileged principal. Each runs as Start-Process -Wait inside a PowerShell thread job, so it is waited for together with everything it started, as when they ran one after the other (a bare WaitForExit() would wait only for the node process). The secondary logon service refused two simultaneous starts once, so the start is retried on that refusal only. Only the service file starts a server and request workers, which take the ports; the platform file drives the controller directly. I could not run PowerShell locally, so the evidence is the CI runs below.

Job and check names, the secrets scan, the second build and the packaging are unchanged. tasks.md has a ticked group 9 for this work.

Removed or merged tests

None. The serial group's heavy tests assert real latency (for example a 4.5 s delayed security query that must take more than 5 s), so they cannot be shortened, and I found no duplicate whose coverage I could name.

Considered and not done

  • Running the serial group's files concurrently, or splitting managed-step-http.test.ts into concurrent files: ports are hash(target) % 4000, so concurrent fixtures can collide and be refused. Giving each fixture targets in a per-file port partition, or a network namespace per file, would work but changes many fixtures (or needs privileges the hosted runner restricts). Follow-up.
  • Making the rendered or native drivers opt-in (the owner left them as they are).
  • Caching bun install on Linux (about 1 s) or Node setup (about 5 s): not worth the cache surface. Windows bun install is about 29 s; left alone.
  • Cutting the post-test steps (second build, SDK check, package, verify): about 6 s, and required.

Follow-ups (not in this PR)

  • Per-fixture port partitions so the serial group's files can run concurrently (the largest remaining cost).
  • tests/backend/delegation-view-service.test.ts failed once with ECONNRESET in a local run at load average 41 (niced parallel group, other work on the machine); it passed three times alone and in every later full run. Cause not established. It may be a keep-alive socket reused after a long synchronous loop starved by load.
  • The cleanup, selection and search browser tests and ui/shared/{app,cleanup,search}.ts were left alone as agreed with the other PR.

Verification

Local, on a 24-core machine shared with other work (load average 5 to 40, so wall-clock is indicative only):

Command Result
bun run build:all, bun run typecheck, bun run tsc --noEmit -p ui/tsconfig.json (before and after) pass
Previous sequence: both typechecks, parallel backend, serial backend, browser and automation 371.6 s (load 5 to 8)
bun run test:all 271.6 s and 276.1 s on the earlier head; 425.9 s on the final head at much higher load, so no figure is claimed for it
node --experimental-strip-types scripts/test.ts --fast, SIGINT after 8 s exits 130, no node --test process left
taskset -c 0,1 node --experimental-strip-types --test --test-name-pattern='portable lanes run every' tests/automation/ci.test.ts passes (it failed on one to three cores before the plan took a core count)

Test counts: backend parallel group 877 tests, 859 pass, 18 skipped; serial group 198 tests, 190 pass, 8 skipped (both unchanged); browser plus automation 1108, all pass (1059 before this PR; the rest are tests merged from dev since, the 16 in the new tests/automation/test-lanes.test.ts, and the plan, built-service and cache tests in ci.test.ts). The five native-only runtime tests are excluded as in CI and were not run; no opencode binary was used.

New automation tests, written first and run against the previous runner (12 failed there; a started-once check for a missing command and the stopped-step-prints-nothing check passed there and stay as guards): each of SIGINT, SIGTERM and SIGHUP stops every step, keeps their output and exits 130, 143 or 129; a grandchild that ignores SIGTERM, and a descendant in its own session holding the pipes, do not hold the runner; a repeated SIGINT is not swallowed; a closed output pipe and a crash of the runner leave no group behind; a step that fails by itself after the first failure is a failure with its output; the heartbeat, the output tail limit and the abandoned leftover pipe holder; the stop command and detaching per platform; the plan on 1, 2, 3, 4 and 24 cores; the CP_BUILT_SERVICE=1 fence; the compile cache folder. node --experimental-strip-types --test tests/automation/*.test.ts and openspec validate release-1-5-2 --strict pass.

CI on this PR (step "Run Linux tests, builds and package checks" and the Windows test step), against the ten recent runs before it:

Before (10 recent runs) This PR (earlier heads, 3 runs) Final head
Linux tests and packages 292 to 313 s 233, 149, 151 s 151, 229 s
Linux tests on latest Node 24 295 to 441 s (three at 425 s or more) 230, 199, 146 s 157, 233 s
Windows fast set 267 to 400 s (typically 312 to 335 s) 217, 263, 278 s 159, 261 s
Windows full set (workflow dispatch on this branch, AP_WINDOWS_FULL=1) 1022 s (main push) 777 s 815 s (run 44323244576, head 3c73f89)

Runner variance is large (the same code took 149 s and 233 s), so read ranges, not single runs.

Pass and skip counts in CI are unchanged: Linux 877/859/18 and 198/190/8 backend; Windows fast set 26 tests, 21 pass, 5 skipped (18/16/2 platform, 8/5/3 service); Windows full set 26 tests, 24 pass, 2 skipped (18/16/2 and 8/8/0), as on main. The longest service-file tests did not move (337 s against 335 s).

Not verified: the Windows stop path of the runner (taskkill /T /F) and the runner on Windows at all; macOS.

Checklist

  • Scope and target branch follow CONTRIBUTING.md.
  • Relevant tests and documentation/contracts are updated, or not applicable.
  • Source PRs contain no generated runtime outputs; a promotion PR into main contains all nine and passes strict rebuild parity.
  • Diff, examples, and attachments contain no credentials, raw logs, private paths/content, or internal tracker data.
  • Third-party license notices are preserved, if applicable.

The backend files that take Setup coordination ports are about two thirds of
the portable Linux step and mostly wait. Run them in one lane next to a second
lane holding both typechecks, the parallel backend group and the browser-model
and automation tests, so the run takes as long as the longer lane. The serial
group stays a single --test-concurrency=1 invocation that nothing joins.

Add test:fast and test:all scripts that share the same plan, print each step's
duration, and stop every lane at the first failure.
@Phototonic Phototonic added documentation Improvements or additions to documentation enhancement New feature or request platform:windows Only happens on Windows platform:linux Only happens on Linux platform:macos Only happens on macOS area:release Packaging, release files and CI labels Nov 18, 2026
Comment thread tests/automation/ci.test.ts Resolved
Comment thread scripts/test-lanes.ts Resolved
@kilo-code-bot

kilo-code-bot Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Incremental static review of 8a5b617. The cleanup regression test now explicitly selects each platform and mocks both signal delivery and command execution, so it cannot invoke real taskkill against a hard-coded PID. No tests were run.

Files Reviewed (1 file)
  • tests/automation/test-lanes.test.ts
Previous Review Summaries (10 snapshots, latest commit 05f89c6)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 05f89c6)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/test-lanes.test.ts 289 On Windows, the new regression test bypasses the mock and invokes real taskkill on a hard-coded PID. It can terminate an unrelated process tree, and the test fails because the mock records no call.

Fix these issues in Kilo Cloud

Files Reviewed (1 file)
  • tests/automation/test-lanes.test.ts - 1 issue

Previous review (commit 985805e)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/test-lanes.test.ts 16 If ps cannot start on a POSIX runner, calling .trim() on missing stdout crashes the test file before any tests register, failing the portable checks.

Fix these issues in Kilo Cloud

Files Reviewed (4 files)
  • CONTRIBUTING.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/test-lanes.ts - 0 issues
  • tests/automation/test-lanes.test.ts - 1 issue

Previous review (commit 4ada204)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
scripts/test-lanes.ts 209 The final sweep signals IDs from already-finished steps. If the OS reuses an ID, cleanup can terminate an unrelated process group or Windows process tree.
tests/automation/test-lanes.test.ts 55 Fixture cleanup converts an empty PID file to 0, so on POSIX it can send SIGKILL to the entire test process group.

Fix these issues in Kilo Cloud

Files Reviewed (4 files)
  • CONTRIBUTING.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • tests/automation/test-lanes.test.ts - 1 issue

Previous review (commit 3c73f89)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
scripts/test-lanes.ts 166 If a step leader exits successfully while a same-group descendant still holds its output pipes, the grace timeout closes the pipes and drops the group without stopping it. The descendant can keep a Setup coordination port bound even after an interrupted run.
tests/automation/test-lanes.test.ts 66 The standalone automation tests expect catchable POSIX signals and POSIX exit codes on Windows. The assertions fail there, and fixture cleanup removes files without terminating surviving child processes.

Fix these issues in Kilo Cloud

Files Reviewed (4 files)
  • .github/workflows/ci.yml - 0 issues
  • tests/automation/workflow-triggers.test.ts - 0 issues
  • scripts/test-lanes.ts - 1 re-verified issue
  • tests/automation/test-lanes.test.ts - 1 re-verified issue

Previous review (commit 11a9a55)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
scripts/test-lanes.ts 166 A successful leader exit can discard the process group while a descendant is still running. The grace timeout closes pipes without stopping the group, so even an interrupted run can leave a Setup port bound for the next run.
tests/automation/test-lanes.test.ts 66 The new POSIX signal cases cannot observe the expected exit codes on Windows, breaking the documented standalone automation run and potentially leaving hanging fixture processes behind.

Fix these issues in Kilo Cloud

Files Reviewed (12 files)
  • .github/workflows/ci.yml - 0 issues
  • CONTRIBUTING.md - 0 issues
  • docs/compatibility.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/ci-backend.ts - 0 issues
  • scripts/ci.ts - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • scripts/test-plan.ts - 0 issues
  • scripts/test.ts - 0 issues
  • tests/automation/ci.test.ts - 0 issues
  • tests/automation/test-lanes.test.ts - 1 issue
  • tests/automation/workflow-triggers.test.ts - 0 issues

Previous review (commit a14b472)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/ci.test.ts 72 On hosts where Node reports three or fewer available CPUs, both parallel test steps also use --test-concurrency=1. The selector matches all three steps and fails the portable suite. Identify the Setup lane independently of worker count.
scripts/test-lanes.ts 60 Signal forwarding is in place, but the runner drops the process group when its leader closes and does not wait for the group to exit. A descendant with independent stdio can still be handling SIGTERM and holding a Setup port when a retry starts. Track the group through shutdown, not just the leader.

Fix these issues in Kilo Cloud

Files Reviewed (7 files)
  • CONTRIBUTING.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/ci.ts - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • scripts/test-plan.ts - 0 issues
  • scripts/test.ts - 0 issues
  • tests/automation/ci.test.ts - 1 issue

Previous review (commit 81953ce)

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 3
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
scripts/test-lanes.ts 38 On POSIX, interrupting the runner can leave detached test processes running and holding Setup coordination ports when a contributor retries. Forward SIGINT and SIGTERM to the active groups and wait for cleanup.
tests/automation/ci.test.ts 72 When Node reports three or fewer available CPUs, all three test steps use --test-concurrency=1, so the assertion that only the Setup step uses it fails. Identify the Setup step independently of worker count.
tests/automation/ci.test.ts 82 If the optional compile-cache directory cannot be created, such as on a read-only dependency mount, the runner falls back to no cache but the new assertion fails the entire portable check. Verify the cache configuration with a writable fixture.

Fix these issues in Kilo Cloud

Files Reviewed (5 files)
  • CONTRIBUTING.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • scripts/test-plan.ts - 0 issues
  • tests/automation/ci.test.ts - 2 issues

Previous review (commit fa38feb)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/ci.test.ts 72 Portable checks fail when Node reports three or fewer available CPUs: all three test commands use --test-concurrency=1, so the assertion that only one command uses it fails. Identify the Setup lane independently of the worker count.
scripts/test-lanes.ts 38 Interrupting the runner on POSIX can leave detached tests running. The runner does not forward SIGINT or SIGTERM to those groups, so Setup fixtures can still hold coordination ports when the next run starts.

Fix these issues in Kilo Cloud

Files Reviewed (5 files)
  • CONTRIBUTING.md - 0 issues
  • docs/compatibility.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • scripts/test-lanes.ts - 1 re-verified issue
  • tests/automation/ci.test.ts - 1 re-verified issue

Previous review (commit 6bc4230)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/ci.test.ts 72 Portable checks fail when Node reports three or fewer available CPUs: all three test steps use --test-concurrency=1, so the test mistakes all three for the Setup lane.
scripts/test-lanes.ts 38 On POSIX, interrupting the runner leaves detached test processes running. Those processes can still hold Setup coordination ports when the next run starts.
Files Reviewed (7 files)
  • .github/workflows/ci.yml - 0 issues
  • CONTRIBUTING.md - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • scripts/test-plan.ts - 0 issues
  • tests/automation/ci.test.ts - 1 issue
  • tests/automation/release.test.ts - 0 issues
  • tests/automation/workflow-triggers.test.ts - 0 issues

Previous review (commit 68b055b)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
tests/automation/ci.test.ts 72 Portable checks fail when Node reports three or fewer available CPUs because the new test mistakes all three test steps for the Setup lane.
scripts/test-lanes.ts 35 Interrupting the runner on POSIX leaves detached test processes running and able to interfere with a retry.
Files Reviewed (11 files)
  • .github/workflows/ci.yml - 0 issues
  • CONTRIBUTING.md - 0 issues
  • openspec/changes/release-1-5-2/tasks.md - 0 issues
  • package.json - 0 issues
  • scripts/ci-backend.ts - 0 issues
  • scripts/ci.ts - 0 issues
  • scripts/test-lanes.ts - 1 issue
  • scripts/test-plan.ts - 0 issues
  • scripts/test.ts - 0 issues
  • tests/automation/ci.test.ts - 1 issue
  • tsconfig.json - 0 issues

Reviewed by gpt-6.2-sol · Input: 21 · Output: 1.5K · Cached: 216.4K

@Phototonic Phototonic mentioned this pull request Nov 18, 2026
5 tasks done
Each test file and each managed-step request worker compiles the same modules
again. The compile cache keys compiled code by source content, so it changes no
test input; it roughly halves the largest serial-group file and shortens the
typechecks.
Comment thread scripts/test-lanes.ts Resolved
Comment thread tests/automation/ci.test.ts Resolved
A signal to the runner did not reach the steps, which run in their own process
groups, so Ctrl-C left them holding Setup ports. Stop every step on SIGINT or
SIGTERM and print what the running steps had written.

Compile cache entries are keyed by file name and the fixtures run from fresh
temporary folders, so a kept cache grew by about 30 MB a run. Empty it at the
start of each run; the speed-up comes from sharing within a run, which is
unchanged. The earlier note that the cache shortens the typechecks was wrong:
their times did not move.

Describe the serial group as latency-bound rather than as waiting.
Runner: record every process group and kill them again once the steps settle and
from an exit hook, so a crash or a closed pipe leaves none behind; handle SIGHUP
and a closed output pipe like SIGINT and SIGTERM; treat a repeated signal, or a
step that has not stopped within ten seconds, as a kill and abandon it even if a
leftover process still holds its pipes; exit 128 plus the signal number when
interrupted; do not detach steps on Windows and stop them with taskkill /T /F;
settle each step once; report a step the runner did not stop as failed with its
output; name the running steps about every minute; keep only the tail of a
step's output; print one line when the compile cache is off.

Plan: take a core count, so one to three cores are tested, and find the serial
step by its lane. Fence plan-cleanup-service.test.ts when CP_BUILT_SERVICE=1: its
built service takes Setup writer slots then, as a listen probe on the bundled
service showed.

Windows job: start each native file under Start-Process -Wait inside a thread
job, so it is waited for with everything it started.
Comment thread scripts/test-lanes.ts Resolved
Comment thread tests/automation/test-lanes.test.ts Resolved
The secondary logon service creates one process at a time and refused the second
Start-Process -Credential when both thread jobs started at once. Retry only that
refusal, up to thirty times a second apart.
A leader that exits 0 while a same-group descendant keeps a pipe open let the
grace period abandon the pipes and forget the group, so the descendant (and any
Setup port it held) outlived the run, and an interrupt during the grace period
did the same. Keep every group recorded whatever the leader's exit status, stop
it (SIGTERM, then SIGKILL after a short bound) before runLanes returns, and
signal the group of a leader that has already exited when the run is stopped.

Skip the process-group and signal cases of the runner tests on Windows, and make
every case stop the fixture processes it recorded, not only delete its files.
Comment thread scripts/test-lanes.ts Resolved
Comment thread tests/automation/test-lanes.test.ts Resolved
… or its tests signal

The runner kept the id of a passing step's group until both lanes finished, so a
reused id could be signalled by the closing sweep (and on Windows taskkill could
hit an exited PID). Sweep each step's group right after its leader exits and its
pipes close, retire a group the moment a probe finds it empty, re-probe before
every signal, never signal a retired group, and leave only unconfirmed groups to
the closing sweep and the exit hook. On Windows run taskkill only against a child
whose exit has not fired. Route every probe and signal through an injectable kill
function and refuse a pid that is not a whole number above 1, itself or its parent.

In the tests, write pid files atomically and have the cleanup accept only a safe
pid, so an empty file (Number('') is 0, the whole process group) is ignored.
Comment thread tests/automation/test-lanes.test.ts Resolved
When ps cannot run, spawnSync has no stdout and trimming it threw while the
module loaded, so no test registered. Read the group with optional chaining and
treat a failed lookup as unknown; cleanup then sends no group signal and signals
only the validated pid itself.
Comment thread tests/automation/test-lanes.test.ts Resolved
…kill

Name the platform on every mocked killTree call and give killTree an injectable
command runner for the Windows path, so no call can shell out to a real taskkill.
Add a mocked win32 call asserting the taskkill command and arguments.
@Phototonic
Phototonic merged commit 5ba4567 into dev Nov 18, 2026
11 checks passed
This was referenced Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:release Packaging, release files and CI documentation Improvements or additions to documentation enhancement New feature or request platform:linux Only happens on Linux platform:macos Only happens on macOS platform:windows Only happens on Windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant