Skip to main content

run-coverage

Runs code coverage checker on the fastest available device. Use when the user asks to run the coverage, or to check the code coverage.

소스 정보

저장소
intentee/llama-cpp-bindings
최근 소스 활동
2026년 5월 25일 12:49
감지된 SKILL.md 언어
영어
스타
1
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
run-coverage
description
Runs code coverage checker on the fastest available device. Use when the user asks to run the coverage, or to check the code coverage.
# Checking the code coverage Run every instrumented test suite in the workspace, picking the fastest compiled device backend for the host, then make sure everything is within required limits. Makefile is the source of truth for the gated values, and the code coverage setup. ## Step 1: detect the device Run this once at the start and echo the chosen device: ```bash if [[ "$OSTYPE" == "darwin"* ]]; then DEVICE=metal elif command -v nvidia-smi >/dev/null 2>&1 && nvidia-smi >/dev/null 2>&1; then DEVICE=cuda else DEVICE=cpu fi echo "Device: $DEVICE" ``` `$DEVICE` selects the backend feature for every suite in Step 2, including `test.unit`. Passing the same device through every target keeps the cmake hash stable, so llama.cpp is compiled once and reused across all suites. ## Step 2: run the suites Translate `$DEVICE` into the value the Makefile expects. `TEST_DEVICE` holds **only** the backend name (`cuda` / `metal` / `vulkan` / `rocm`), or empty for CPU since there is no `cpu` feature: ```bash [ "$DEVICE" = "cpu" ] && FEAT= || FEAT="$DEVICE" ``` Then run exactly: ```bash make coverage TEST_DEVICE="$FEAT" ``` ## Step 4: report After all suites finish, sum up the results in an actionable report. Make sure all code coverage gates are met.
GitHub에서 보기