• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

llamastash / llamastash / 26778936539
87%

Build:
DEFAULT BRANCH: main
Ran 01 Jun 2026 08:14PM UTC
Jobs 1
Files 190
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

01 Jun 2026 08:06PM UTC coverage: 86.333% (+0.009%) from 86.324%
26778936539

push

github

web-flow
fix: Windows model-launch backend + Host-panel RAM/UMA + daemon self-heal (#11)

* fix(gpu): unify hardware-info codepath; fix Host-panel RAM + UMA star

The Host panel showed a wrong RAM value and a spurious unified `*` on
Windows AMD while `init` was correct. Two root causes: the DXGI probe
inferred UMA from `SharedSystemMemory` (~half system RAM on every
adapter, discrete included), and the host pane then subtracted those
bytes from the RAM gauge.

- Add `GpuInfo::is_unified()` as the single source of truth for the
  unified-memory decision; both init and the host pane derive from it.
- Host pane no longer subtracts UMA bytes: RAM always shows the true
  sysinfo total (matching init); a derived `unified` flag drives `RAM*`.
- DXGI: detect genuine UMA via the authoritative D3D12 `UMA` architecture
  flag instead of the shared-memory heuristic; fold the shared pool into
  VRAM total only for true APUs.

Linux / macOS / NVIDIA paths unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(cli): self-heal stale runtime.json so the daemon auto-respawns

After an unclean daemon exit (crash, `daemon stop --force`, power loss)
the leftover runtime.json pointed at a dead control plane. `Client::connect`
doesn't probe reachability, so `connect_or_spawn` trusted the file and
every call failed instead of auto-spawning — the TUI/CLI could never
restart the daemon until the file was hand-deleted.

- connect_or_spawn now gates the "runtime.json present" path on the PID
  lock (OS-released the instant the daemon dies, on both flock and
  LockFileEx). If no live daemon holds it, clear the stale runtime.json
  and auto-spawn. Spawn logic factored into `spawn_and_attach`.
- `daemon stop --force` removes the runtime.json it orphans (the hard
  kill skips the daemon's own shutdown cleanup).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(init): route Windows AMD GPUs to the Vulkan llama.cpp build

`win-hip-rad... (continued)

104 of 121 new or added lines in 27 files covered. (85.95%)

20 existing lines in 8 files now uncovered.

42229 of 48914 relevant lines covered (86.33%)

1630.37 hits per line

Uncovered Changes

Lines Coverage ∆ File
11
47.88
2.42% src/cli/client.rs
3
85.57
-2.21% src/gpu/mod.rs
2
98.3
-0.33% src/tui/info_pane.rs
1
83.71
-0.05% src/cli/daemon.rs

Coverage Regressions

Lines Coverage ∆ File
8
65.89
-6.2% src/cli/logs.rs
4
97.0
-0.92% tests/start_model_ipc_test.rs
2
90.16
-3.28% src/daemon/resources.rs
2
92.35
-0.3% tests/cli_integration_test.rs
1
83.71
-0.05% src/cli/daemon.rs
1
83.85
-0.18% src/daemon/supervisor.rs
1
95.48
-0.65% src/discovery/metadata_cache.rs
1
95.62
-0.73% src/proxy/eviction.rs
Jobs
ID Job ID Ran Files Coverage
1 26778936539.1 01 Jun 2026 08:14PM UTC 190
86.33
GitHub Action Run
Source Files on build 26778936539
  • Tree
  • List 190
  • Changed 37
  • Source Changed 30
  • Coverage Changed 25
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #26778936539
  • cf1ed385 on github
  • Prev Build on main (#26766239497)
  • Next Build on main (#26780119647)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc