llama.cpp decision runner (D41): reproducible build pipeline + smoke-tested release binary

未關閉
#9 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
cmake, git, rust

研究方向

Start with forks/llama.cpp/build.sh, then read forks/llama.cpp/README.md, docs/FORK_LLAMA_SERVER.md, and the just build-llama-fork recipe. Run the documented CPU build from a fresh clone and record its output; completion requires a provenance manifest and a smoke-tested llama-server that returns a per-choice distribution from a real GGUF at /v1/decision.

由索引模型根據 Issue 內容生成。

描述

Context

D41 established branch-only tracking of a llama.cpp decision-inference fork: base `thecodacus/llama.cpp` @ `parallel-decision` (tree-mode `POST /v1/decision`), plus fast-LoRA kernels when a CUDA port exists (RESEARCH §28; 1Cat-vLLM recorded as V100/SM70 informatics reference only — serving path stays llama.cpp static binary, no Python at runtime).

The skeleton landed on main (c2fec9a) but the tracked pipeline never produced a binary:

  • `forks/llama.cpp/build.sh` defaulted to `github.com/opencodifier/llama.cpp` — 404 (fork never promoted); real base is `thecodacus/llama.cpp`
  • CMake flags were invented names (`LLAMA_SERVER`, `LLAMA_EXAMPLES`, `GGML_STRIP`) that silently defaulted everything ON — correct names are `LLAMA_BUILD_*`
  • `LLAMA_BUILD_TOOLS=OFF` silently removes the `llama-server` target (server lives under `tools/server/`)
  • Historical ad129b0/38de7eb builds were ad hoc, never through this script — nothing reproducible to release
  • No branch: skeleton work went straight to main

Scope (this ticket, branch `fork/llama-decision-2026-10`)

Working worktree: `/nas/Temp/repos/OpenCodifier-fork` (separate from main working tree).

  • `build.sh`: correct repo URL, correct `LLAMA_BUILD_*` flags, `BACKEND=cpu|cuda|vulkan`, provenance manifest (`BUILD-INFO.txt`: base/final commit, backend, host, UTC)
  • `forks/llama.cpp/.gitignore` so `build/`, clone, and logs never pollute commits
  • Working compiled binary: `BACKEND=cpu` build completes; binary produced at `forks/llama.cpp/build/bin/llama-server`
  • Smoke test: built binary serves `POST /v1/decision` against a real GGUF and returns a per-choice distribution; commands + output recorded in the ticket
  • Docs aligned: `forks/llama.cpp/README.md` + `docs/FORK_LLAMA_SERVER.md` real repo URL; `just build-llama-fork` recipe verified against the new script
  • `BACKEND=cuda` path documented for T5500/V100 builds (build executed there later)
  • PR through the DevOps pipeline (CI = `.gitforge.yml` gates)

Explicitly out of scope (linked, other sessions)

  • Fast-LoRA kernel A/B (woct0rdho CUDA port does not exist yet — §28) → follow-up after this lands
  • Fork CI smoke-build job → follow-up once the build recipe is stable here
  • D42 e2e test fix, main-tree CI gates, E1-G eval wrap → main-session work, untouched by this branch

Acceptance

A fresh clone of this branch + `cd forks/llama.cpp && BACKEND=cpu ./build.sh` yields a working `llama-server` whose `/v1/decision` answers a real request, with the build provenance in `BUILD-INFO.txt`.

主要語言
Rust
星號
1
分支
0
平均合併
13 小時 10 分鐘
30 天內合併 PR
12

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

aliasfoxkde/OpenCodifier 的其他 Issue

查看 aliasfoxkde/OpenCodifier 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。