Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
5920576
fix(lemonade): pin Lemonade 2026.44.1 so a ROCm 10.1 SDK gets a ROCm …
rominf Nov 3, 2026
fb07c90
test(e2e): compare the Lemonade archive extension ignoring case
rominf Nov 3, 2026
a7c305c
fix(lemonade): refuse a host too old for the pinned lemond up front
rominf Nov 10, 2026
a6adb69
fix(lemonade): refuse a host whose loader cache has no libssl.so.3
rominf Nov 11, 2026
202490c
test(e2e): stop calling Lemonade 11.5.1 the pin in two Windows rows
rominf Nov 11, 2026
0b2add5
test(e2e): check the llama.cpp ROCm tag where the SDK is the packaged…
rominf Nov 13, 2026
3ab5ec0
Merge remote-tracking branch 'origin/main' into fix/lemonade-2026.44
rominf Nov 13, 2026
65c9bc8
Merge remote-tracking branch 'origin/main' into fix/lemonade-2026.44
rominf Nov 16, 2026
96956bf
style(lemonade): cargo fmt the spawn helpers
rominf Nov 16, 2026
c03c7b0
test(e2e): stop calling Lemonade 11.5.1 the pin in a row-scope test c…
rominf Nov 16, 2026
2a6520a
Merge remote-tracking branch 'origin/main' into fix/lemonade-2026.44
rominf Nov 16, 2026
9764b29
fix(lemonade): add an opt-out for the host-library check, and say wha…
rominf Nov 17, 2026
ff1673d
Merge remote-tracking branch 'origin/main' into fix/lemonade-2026.44
rominf Nov 17, 2026
9605dbb
fix(lemonade): compile the host-refusal outcome helpers on Linux only…
rominf Nov 17, 2026
3779afb
docs: stop saying every published Lemonade build needs glibc 2.38
rominf Nov 17, 2026
391bea4
fix(lemonade): read the backend state at its column, and name the ver…
rominf Nov 17, 2026
9ee7338
docs: list the new parser tests, drop unverifiable release-cadence fi…
rominf Nov 17, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

13 changes: 9 additions & 4 deletions MANIFEST.md
Original file line number Diff line number Diff line change
Expand Up @@ -714,11 +714,16 @@ Lemonade embeddable archive from the official Lemonade SDK GitHub releases at
to the rocm-cli managed data directory and is reused for subsequent
`rocm engines start lemonade` invocations. This is a self-contained binary
distribution; no Python packages are installed for Lemonade by rocm-cli.
On Linux/WSL, `rocm engines install lemonade` may also query
`https://api.github.com/repos/lemonade-sdk/llama.cpp/releases/latest` (an
unauthenticated call) while aligning Lemonade's `llamacpp:rocm` backend to
the active ROCm SDK version; see
On Linux/WSL and Windows, `rocm engines install lemonade` may also list
`https://api.github.com/repos/lemonade-sdk/llama.cpp/releases` (the 30 newest
releases, one unauthenticated call) while aligning Lemonade's `llamacpp:rocm`
backend to the active ROCm SDK version; see
[Lemonade backend alignment on engine install](docs/engine-plugins.md#lemonade-backend-alignment-on-engine-install).
Lemonade itself then downloads the llama.cpp backend it installs from the
`lemonade-sdk/llama.cpp` GitHub releases, and the ROCm runtime that backend
runs on from AMD's ROCm package repository (as Python wheels into a virtual
environment of Lemonade's own, or as a TheRock tarball); those downloads are
Lemonade's, not rocm-cli's.

### Engine-Specific Python Dependencies

Expand Down
20 changes: 16 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,22 @@ serving is Linux or WSL2 only (see [docs/vllm.md](docs/vllm.md)).

The minimum supported Linux release, native or under WSL2, is Ubuntu 24.04. On

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph correctly retires the old "every published build of it needs those versions" framing (2026.45.3 needs more), and the refusal-describing sentence later on is correctly scoped to glibc/libssl.so.3 only. But the identical old framing — "every published Lemonade embeddable requires/is linked against glibc 2.38 (and GLIBCXX_3.4.32)" — is left unedited in several other places this PR doesn't touch, two of which are strings printed directly to users:

  • docs/wsl.md:18-20
  • crates/rocm-core/src/fix/catalog.rs's fix-wsl-5-distro-too-old rationale (printed by rocm fix)
  • crates/rocm-core/src/diagnose/wsl.rs's matching notes (printed by rocm diagnose)
  • crates/rocm-core/src/examine.rs's WSL_MIN_UBUNTU doc comment (says "See docs/wsl.md")
  • skills/rocm-doctor/reference.md:188

AGENTS.md §5 names exactly this failure mode: a behavior claim repeating across docs and printed CLI output, each drifting independently. Since this PR is what invalidates the "every published build" framing (by introducing 2026.45.3 as the counter-example), the sibling surfaces should get the same "2026.44.1 needs this; the newest release needs more" nuance.

Confidence 90 · mechanical

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 3779afb. Four of the five places now name the pinned build instead of "every published" one, and add that newer Lemonade releases need more:

  • docs/wsl.md
  • the fix-wsl-5-distro-too-old rationale rocm fix prints (fix/catalog.rs)
  • the matching note rocm diagnose prints (diagnose/wsl.rs)
  • WSL_MIN_UBUNTU's doc comment (examine.rs)

The printed strings do not name a version, so they stay true across bumps. No test pins that text, and cargo xtask catalog --check passes (the generated catalog does not carry it).

I left skills/rocm-doctor/reference.md alone. Its row says "the 2.38 / GLIBCXX_3.4.32 the engines need", which is true of the pinned build and does not make the "every published" claim. It is also a parsed e2e fixture.

On GLIBCXX (from the review body): the README now says that the check reads glibc and OpenSSL only, and that GLIBCXX_3.4.32 (libstdc++) is not checked.

other distributions the equivalent requirement is glibc 2.38 with
`GLIBCXX_3.4.32`: that is what the Lemonade engine is linked against, and every
published build of it needs those versions, so there is no older release to fall
back to. Ubuntu 22.04 ships glibc 2.35 and cannot run it; Ubuntu 24.04 provides
glibc 2.39 and `GLIBCXX_3.4.33`.
`GLIBCXX_3.4.32`, and OpenSSL 3.0.0 or newer (`libssl.so.3`): that is what the
Lemonade engine is linked against. Every stable Lemonade release from 11.5.1
through 2026.44.1, the one rocm-cli pins, needs those versions; the newest,
2026.45.3, needs glibc 2.43 and OpenSSL 3.2.0, which is why it is not pinned.
Ubuntu 22.04 ships glibc 2.35 and cannot run it; Ubuntu 24.04 provides glibc
2.39, `GLIBCXX_3.4.33` and OpenSSL 3.0.13. On an older host,
`rocm engines install lemonade` stops before downloading anything and says what
falls short: the glibc version Lemonade needs and the newest the host's
`libc.so.6` provides, or that
the host has no `libssl.so.3`, the library of OpenSSL 3. That check reads glibc
and OpenSSL only; `GLIBCXX_3.4.32` (libstdc++) is not checked. Where Lemonade is
already installed, the same check refuses to reinstall it or start it, and says
the installed copy was left as it is. The check reads the `ldconfig` cache, so a
host that provides these libraries some other way (`LD_LIBRARY_PATH`, a Nix or
Guix profile) can set `ROCM_CLI_DISABLE_LEMONADE_HOST_LIBRARY_CHECK=1`: the
shortfall is then printed as a warning and Lemonade goes ahead.

> [!IMPORTANT]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The claim that the message names the OpenSSL version "the host has" is not reachable on a pre-3.x host with the real probe (see the comment in host_libraries.rs); the e2e scenario only gets there through the hook override. Either fix the probe or narrow this wording.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in a6adb69. The README now says what the probe can report: the glibc version needed and the one the host has, or that the host has no libssl.so.3, the library of OpenSSL 3. The PR body example is now an Ubuntu 20.04 host (glibc 2.31, OpenSSL 1.1 only), which is the message the real probe produces there.

> **Tech Preview:** This software is provided as-is, without warranty or
Expand Down
4 changes: 2 additions & 2 deletions crates/e2e-report/src/consolidated/markdown.rs
Original file line number Diff line number Diff line change
Expand Up @@ -778,7 +778,7 @@ mod tests {
let platform = r#"{
"platform_slug": "mi300x",
"capability": {"effective_serve_engine": "vllm"},
"versions": {"os":"Ubuntu 24.04.3 LTS","rocm":"7.13.0","vllm":"0.23.0+rocm723","lemonade":"11.5.1"},
"versions": {"os":"Ubuntu 24.04.3 LTS","rocm":"7.13.0","vllm":"0.23.0+rocm723","lemonade":"2026.44.1"},
"expectations": [
{"id":"serve-x","effective_engine":"vllm","expected":"pass"}
]
Expand All @@ -790,7 +790,7 @@ mod tests {
"Ubuntu 24.04.3 LTS",
"ROCm 7.13.0",
"vLLM 0.23.0+rocm723",
"lemonade 11.5.1",
"lemonade 2026.44.1",
] {
assert!(md.contains(token), "matrix cell missing {token:?}:\n{md}");
}
Expand Down
2 changes: 1 addition & 1 deletion crates/rocm-core/src/diagnose/wsl.rs
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,7 @@ pub(super) fn check_wsl_5_distro_too_old(e: &Examination, _symptom: &str) -> Dia
verify: "f=/etc/os-release; [ -e \"$f\" ] || f=/usr/lib/os-release; grep VERSION_ID \"$f\" 2>/dev/null | head -1"
.to_owned(),
notes: vec![
"This is a hard floor, not a recommendation: Ubuntu 22.04 ships glibc 2.35, below the glibc 2.38 / GLIBCXX_3.4.32 that every published Lemonade embeddable is linked against, so the engine cannot start there at all.".to_owned(),
"This is a hard floor, not a recommendation: Ubuntu 22.04 ships glibc 2.35, below the glibc 2.38 / GLIBCXX_3.4.32 that the pinned Lemonade embeddable is linked against (newer Lemonade releases need more), so the engine cannot start there at all.".to_owned(),
],
..Fix::default()
};
Expand Down
4 changes: 2 additions & 2 deletions crates/rocm-core/src/examine.rs
Original file line number Diff line number Diff line change
Expand Up @@ -86,8 +86,8 @@ pub struct Device {
/// The oldest distro release the WSL path supports.
///
/// Ubuntu 22.04 ships glibc 2.35, below the glibc 2.38 / `GLIBCXX_3.4.32` floor
/// every published Lemonade embeddable is linked against, so the engine cannot
/// start there. See `docs/wsl.md`.
/// the pinned Lemonade embeddable is linked against (newer Lemonade releases
/// need more), so the engine cannot start there. See `docs/wsl.md`.
pub const WSL_MIN_UBUNTU: (u32, u32) = (24, 4);

/// WSL2-specific machine state. `None` on every other platform.
Expand Down
2 changes: 1 addition & 1 deletion crates/rocm-core/src/fix/catalog.rs
Original file line number Diff line number Diff line change
Expand Up @@ -732,7 +732,7 @@ pub(super) const RECIPES: &[FixRecipe] = &[
FixRecipe {
fix_id: "fix-wsl-5-distro-too-old",
title: "Move to a distro release the WSL path supports",
rationale: "Ubuntu 22.04 ships glibc 2.35, below the glibc 2.38 / GLIBCXX_3.4.32 floor every published Lemonade embeddable is linked against, so the engine cannot start there at all. This is a hard floor, not a recommendation.",
rationale: "Ubuntu 22.04 ships glibc 2.35, below the glibc 2.38 / GLIBCXX_3.4.32 floor the pinned Lemonade embeddable is linked against (newer Lemonade releases need more), so the engine cannot start there at all. This is a hard floor, not a recommendation.",
commands: &[
"# From Windows, install a supported distro alongside the current one:",
"# wsl --install -d Ubuntu-24.04",
Expand Down
3 changes: 2 additions & 1 deletion crates/rocm-core/src/host_gpu.rs
Original file line number Diff line number Diff line change
Expand Up @@ -83,12 +83,13 @@ use windows_inventory::{
};
#[cfg(target_os = "linux")]
use wsl::detect_wsl_windows_display_probe_text;
pub use wsl::ldconfig_cache;
#[cfg(test)]
use wsl::local_windows_host_driver_probe;
pub use wsl::{WSL_ROCDXG_READY, WslHostDriverProbe, is_wsl_host};
pub(crate) use wsl::{
detect_local_windows_host_driver, detect_wsl_host_driver, detect_wsl_summary, is_wsl1_kernel,
ldconfig_cache, ldconfig_lists_librocdxg,
ldconfig_lists_librocdxg,
};
use wsl::{detect_wsl_windows_display_gfx_target_fast, wsl_driver_summary};

Expand Down
2 changes: 1 addition & 1 deletion crates/rocm-core/src/host_gpu/wsl.rs
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ pub(crate) fn is_wsl1_kernel(kernel_release: &str) -> bool {
/// Deliberately not routed through [`host_path`]: these are programs this
/// process executes, not files it reads to describe the machine, and a
/// simulated host root holds no working linker to run.
pub(crate) fn ldconfig_cache() -> Option<String> {
pub fn ldconfig_cache() -> Option<String> {
for program in ["ldconfig", "/sbin/ldconfig", "/usr/sbin/ldconfig"] {
if let Some(text) = capture_optional_command(program, &["-p"]) {
return Some(text);
Expand Down
3 changes: 2 additions & 1 deletion crates/rocm-core/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,7 @@ pub use gfx_target::{
normalize_therock_family,
};
pub use hardware_root::host_path;
pub use host_gpu::ldconfig_cache;
pub use host_gpu::{
DriverSummary, ExamineSummary, HostGpuSummary, WSL_ROCDXG_READY, WindowsGpuListing,
WslHostDriverProbe, WslSummary, default_engine_for_host, default_engine_for_platform,
Expand All @@ -152,7 +153,7 @@ pub use host_gpu::{
use host_gpu::{KfdGpuNode, kfd_gpu_nodes_in};
use host_gpu::{
detect_linux_sysfs_gfx_target, detect_local_windows_host_driver, detect_wsl_host_driver,
detect_wsl_summary, is_wsl1_kernel, ldconfig_cache, ldconfig_lists_librocdxg,
detect_wsl_summary, is_wsl1_kernel, ldconfig_lists_librocdxg,
};
pub use jsonl_store::jsonl_lock_path;
pub use log_tail::{
Expand Down
4 changes: 2 additions & 2 deletions crates/rocm-deps/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,14 @@ include!(concat!(env!("OUT_DIR"), "/pins.rs"));
/// GitHub repository publishing the Lemonade embeddable release archives.
pub const LEMONADE_GITHUB_REPO: &str = "lemonade-sdk/lemonade";

/// Strip a leading `v` from a release tag (`v11.5.1` -> `11.5.1`).
/// Strip a leading `v` from a release tag (`v2026.44.1` -> `2026.44.1`).
#[must_use]
pub fn strip_v(tag: &str) -> &str {
tag.strip_prefix('v').unwrap_or(tag)
}

/// Name of the Lemonade embeddable archive for a host token and extension,
/// e.g. `lemonade-embeddable-11.5.1-ubuntu-x64.tar.gz`.
/// e.g. `lemonade-embeddable-2026.44.1-ubuntu-x64.tar.gz`.
#[must_use]
pub fn lemonade_archive_name(version: &str, os_arch: &str, extension: &str) -> String {
format!(
Expand Down
5 changes: 3 additions & 2 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -663,9 +663,10 @@ The Lemonade engine adapter (`rocm-engine-lemonade`): installs the embeddable Le
| [`device_policy.rs`](../engines/lemonade/src/device_policy.rs) | Device policy and GPU selection: the GPU-required check, `--device`/`--gpu` parsing, the GPU ordinals to pin before a launch, the device availability `detect` reports, and the notice that names a non-ROCm GPU backend (Vulkan) as the one serving. | domain |
| [`direct_llama.rs`](../engines/lemonade/src/direct_llama.rs) | Hugging Face checkpoint and GGUF resolution, including a registered model name resolved through the installed Lemonade catalog, which route a name serves by, and the direct serve path that runs a packaged `llama-server` on a GGUF (`serve_direct_llama_server`). | domain |
| [`footprint.rs`](../engines/lemonade/src/footprint.rs) | What a Lemonade install costs on disk: the pre-install notice and free-space check, and the read-only view of Lemonade's install trees and record. | domain |
| [`install.rs`](../engines/lemonade/src/install.rs) | Embeddable-runtime download, extraction orchestration and manifest persistence, plus the `LemonadeRuntime` handle and `resolve_runtime` over the persisted manifest. | domain |
| [`host_libraries.rs`](../engines/lemonade/src/host_libraries.rs) | Whether this host's glibc and OpenSSL are new enough for the pinned Linux `lemond`: reads the newest `GLIBC_*`/`OPENSSL_*` version node the loader cache's `libc.so.6` and `libssl.so.3` define, or finds that a cache listing `libc.so.6` has no `libssl.so.3`, and refuses before download and before `lemond` starts, naming what is needed and what the host has. | domain |
| [`install.rs`](../engines/lemonade/src/install.rs) | Embeddable-runtime download, extraction orchestration and manifest persistence, the pinned archives' digests with what the Linux `lemond` needs from the host (`LINUX_LEMOND_NEEDS`), plus the `LemonadeRuntime` handle and `resolve_runtime` over the persisted manifest. | domain |
| [`llamacpp_backend.rs`](../engines/lemonade/src/llamacpp_backend.rs) | llama.cpp backend discovery and selection: asks `lemonade backends` what the host supports, picks and installs the best GPU backend, and finds its `llama-server`. | domain |
| [`process.rs`](../engines/lemonade/src/process.rs) | `lemond` spawn, environment and path setup, readiness and health polling, and the background relaunch of the `serve-http` command. | domain |
| [`process.rs`](../engines/lemonade/src/process.rs) | `lemond` spawn (refused on Linux for a host older than the pinned build needs), environment and path setup, readiness and health polling, and the background relaunch of the `serve-http` command. | domain |
| [`router_serve.rs`](../engines/lemonade/src/router_serve.rs) | The router serve path: spawn `lemond`, select a GPU backend, load and verify the model by its router name, and on a failure after the spawn stop the server and settle the state, except that a state file that is empty, torn or not a JSON object refuses the `failed` mark and is left as it was. A load or verification failure may then be served directly; a probe that could not reach the endpoint is not one. | domain |
| [`runtime_dir.rs`](../engines/lemonade/src/runtime_dir.rs) | `XDG_RUNTIME_DIR` tier 1, 2 and 3 hardening for the spawned child. | domain |
| [`state.rs`](../engines/lemonade/src/state.rs) | Service state file I/O and port and endpoint helpers. Every state write goes through rocm-core's locked, atomic `write_json_state_file`/`merge_json_state_file`, so a merge into an empty, torn or non-object state file is refused and leaves it as it was. | domain |
Expand Down
52 changes: 42 additions & 10 deletions docs/engine-plugins.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,21 @@ The rewrite tries two builds in order. The first keeps Lemonade's own pinned
llama.cpp release and just repoints it at the active ROCm version — a
deliberate, reproducible pin. If that attempt fails to resolve against the
installed backend's shared libraries — for example because that release never
shipped an asset for the active ROCm version — the second queries GitHub's
`releases/latest` for `lemonade-sdk/llama.cpp` (an unauthenticated
`api.github.com` call, subject to GitHub's public rate limit) and installs
whatever build is newest at that moment. That second build is a moving
target, not a pin: which llama.cpp commit actually gets installed depends on
when the install ran, and the version installed is not recorded anywhere
`rocm examine`/`rocm version` report. An attempt that cannot be verified
against the installed backend's shared libraries reverts to whichever version
shipped an asset for the active ROCm version — the second lists the 30 newest
`lemonade-sdk/llama.cpp` releases on GitHub (an unauthenticated
`api.github.com` call, subject to GitHub's public rate limit) and installs the
most recently published one that ships the llama.cpp archive for the active
ROCm version's `major.minor` on this platform
(`llama-<tag>-bin-ubuntu-rocm-<major.minor>-x64.tar.gz` on Linux,
`llama-<tag>-bin-win-rocm-<major.minor>-x64.zip` on Windows). The newest
release alone is not used, because a release can be published without its
ROCm archives. The second attempt is skipped when none of the 30 ships that
archive, when the listing cannot be fetched, and when the build it finds is the
one Lemonade already pins (the first attempt tried that build). That second
build is a moving target, not a pin: which llama.cpp commit actually gets
installed depends on when the install ran, and the version installed is not
recorded anywhere `rocm examine`/`rocm version` report. An attempt that cannot
be verified against the installed backend's shared libraries reverts to whichever version
was pinned before the attempt — the packaged pin on a fresh install or after
`--reinstall`, but whatever alignment last wrote otherwise — rather than
being kept.
Expand Down Expand Up @@ -132,8 +139,33 @@ The versions of the third-party runtimes rocm-cli downloads are pinned in
`runtime-deps.toml` at the repository root — one `[runtime.<name>]` table per
runtime. That file is the only place a runtime version is written down:
archive names, download URLs, and the dashboard's offline fallback are all
derived from it, so a bump is a one-line edit and the tree cannot end up
holding two different versions of the same runtime.
derived from it, so the tree cannot end up holding two different versions of
the same runtime. A Lemonade bump also records the new release's archive
digests (`EMBEDDABLE_LINUX_SHA256` and `EMBEDDABLE_WINDOWS_SHA256` in
[install.rs](../engines/lemonade/src/install.rs)): the downloaded archive is
checked against them, and a digest cannot be derived from the version. It also
re-reads what the new Linux `lemond` needs from the host, the newest `GLIBC_*`
and `OPENSSL_*` versions `objdump -T lemond` lists, into `LINUX_LEMOND_NEEDS`
beside those digests; a unit test fails until that record names the new Linux
archive. On Linux, `rocm engines install lemonade` refuses a host whose glibc
or OpenSSL is older than that before downloading anything, and the engine
refuses to start that `lemond` on such a host
([host_libraries.rs](../engines/lemonade/src/host_libraries.rs)). For each
library that falls short, the message names the version needed and what the
host has: its version, read from the library the `ldconfig` cache lists, or
that the cache has no such library at all. A host with only OpenSSL 1.1 has no
`libssl.so.3`, so it reads that way. A host whose cache cannot be read, or
whose library does not parse, is not refused. A refused install says what it
left undone: "Nothing was downloaded." for a fresh install, or that the
Lemonade already installed there stays as it is. Because only the `ldconfig`
cache is read, a host that provides OpenSSL 3 or glibc outside it
(`LD_LIBRARY_PATH`, a Nix or Guix profile, a user prefix, a stale cache) is
refused although `lemond` could load there; setting
`ROCM_CLI_DISABLE_LEMONADE_HOST_LIBRARY_CHECK` (any value) turns both refusals
into a warning, and the refusal message names it. Lemonade
2026.44.1, the current pin, needs glibc 2.38 and OpenSSL 3.0.0, which Ubuntu
24.04 meets; 2026.45.3's `lemond` needs glibc 2.43 and OpenSSL 3.2.0, which it
does not.

`rocm engines list` shows the exact plugin directories for the current host.
The same output is available in the TUI with `/engine`.
Expand Down
27 changes: 27 additions & 0 deletions docs/manual-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -469,6 +469,33 @@ folder run `rocm engines install lemonade --yes`. Expected result:
carries on: Lemonade picks the backend after this point and a smaller one may
fit. (Stop it before the download if you do not want one.)

To check the refusal of a Linux or WSL host too old for the pinned Lemonade
server (no download needed): the pinned build needs glibc 2.38 and OpenSSL 3
(`libssl.so.3`). On a real older host, such as Ubuntu 22.04 (glibc 2.35) or
Ubuntu 20.04 (glibc 2.31, OpenSSL 1.1 only), run
`rocm engines install lemonade --yes` in a fresh data folder. On a newer host,
use a build with the `rocm/e2e-test-hooks` feature and set `ROCM_E2E_LEMONADE_HOST_GLIBC=2.31` and
`ROCM_E2E_LEMONADE_HOST_OPENSSL=missing` first. Expected result:

- It fails with `this host's libraries are too old for the Lemonade <version>
server: it needs glibc 2.38 or newer (this host's libc.so.6 provides up to
GLIBC_<version>)`, followed
on a host without OpenSSL 3 by `and OpenSSL 3.0.0 or newer (this host's loader
cache has no libssl.so.3)`, then `Nothing was downloaded.`, and ends by
naming `ROCM_CLI_DISABLE_LEMONADE_HOST_LIBRARY_CHECK=1` as the way to skip
the check.
- The data folder's `engines/lemonade` has no `downloads` or `runtime`
subfolder, and `rocm storage report` lists no Lemonade install.
- Run it again with `ROCM_CLI_DISABLE_LEMONADE_HOST_LIBRARY_CHECK=1`: it prints
the same shortfall as a `warning:` ending `going ahead because
ROCM_CLI_DISABLE_LEMONADE_HOST_LIBRARY_CHECK is set.` and goes on to install
(on a real older host the server then fails to start).
- Where the pinned Lemonade is already installed, the refusal ends `Nothing was
changed: the Lemonade <version> already installed in <folder> stays as it is,
but its server cannot start on this host either.` instead, and that folder is
unchanged.
- On Ubuntu 24.04 or newer the same command installs Lemonade as usual.

With room to spare, on Windows from an interactive console: install Lemonade
with no runtime active, then `rocm install sdk`, then `rocm serve <gguf-model>`.
Expected result:
Expand Down
Loading
Loading