Skip to content

feat(harness): add OMP client support - #603

Draft
Graffioh wants to merge 1 commit into
Luce-Org:mainfrom
Graffioh:agent/omp-harness-support
Draft

feat(harness): add OMP client support#603
Graffioh wants to merge 1 commit into
Luce-Org:mainfrom
Graffioh:agent/omp-harness-support

Conversation

@Graffioh

@Graffioh Graffioh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add OMP as a first-class Lucebox harness using its custom openai-responses provider support
  • install the official OMP prebuilt binary under .harness-work/clients/omp
  • add launcher timeout/configuration contracts, backend-pair routing, result summarization, CTest registration, and documentation

Validation

  • bash harness/tests/test_run_omp_config.sh harness/clients/run_omp.sh
  • REAL_OMP_BIN=/home/berto/.local/bin/omp bash harness/tests/test_run_omp_config.sh harness/clients/run_omp.sh
  • bash harness/tests/test_client_launcher_timeouts.sh
  • bash harness/tests/test_run_pi_timeout.sh harness/clients/run_pi.sh
  • python3 -m py_compile harness/client_test_runner.py harness/clients/summarize_backend_pair.py
  • uv run --frozen --extra dev ruff check .
  • official OMP v17.2.15 binary installation smoke via client_test_runner.py install --clients omp

Deferred validation

  • Run harness/clients/run_omp.sh against a live Lucebox model when GPU capacity is available
  • Optionally compare Lucebox and llama.cpp with CLIENT=omp harness/clients/run_backend_pair.sh

This is intentionally a draft until the live GPU-backed client run is complete.

Review in cubic

@Graffioh
Graffioh force-pushed the agent/omp-harness-support branch from 78b6939 to 68af86a Compare August 12, 2026 20:59
@Graffioh Graffioh changed the title Add OMP harness support feat(harness): add OMP client support Aug 12, 2026
@Graffioh

Copy link
Copy Markdown
Contributor Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@Graffioh I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

1 issue found across 12 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="harness/clients/run_omp.sh">

<violation number="1" location="harness/clients/run_omp.sh:12">
P3: OMP_TIMEOUT is validated only inside run_with_timeout after the server is started and models.yml is written, while OMP_STREAM_IDLE_TIMEOUT_MS is validated up front. Validate OMP_TIMEOUT (non-negative integer, 0 allowed) before sourcing/starting so an invalid deadline fails fast with a clear message.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

: "${OMP_TOOLS:=read,grep,glob}"
: "${OMP_TIMEOUT:=3600}"
: "${OMP_STREAM_IDLE_TIMEOUT_MS:=3600000}"
if [[ ! "$OMP_STREAM_IDLE_TIMEOUT_MS" =~ ^[1-9][0-9]*$ ]]; then

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P3: OMP_TIMEOUT is validated only inside run_with_timeout after the server is started and models.yml is written, while OMP_STREAM_IDLE_TIMEOUT_MS is validated up front. Validate OMP_TIMEOUT (non-negative integer, 0 allowed) before sourcing/starting so an invalid deadline fails fast with a clear message.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At harness/clients/run_omp.sh, line 12:

<comment>OMP_TIMEOUT is validated only inside run_with_timeout after the server is started and models.yml is written, while OMP_STREAM_IDLE_TIMEOUT_MS is validated up front. Validate OMP_TIMEOUT (non-negative integer, 0 allowed) before sourcing/starting so an invalid deadline fails fast with a clear message.</comment>

<file context>
@@ -0,0 +1,81 @@
+: "${OMP_TOOLS:=read,grep,glob}"
+: "${OMP_TIMEOUT:=3600}"
+: "${OMP_STREAM_IDLE_TIMEOUT_MS:=3600000}"
+if [[ ! "$OMP_STREAM_IDLE_TIMEOUT_MS" =~ ^[1-9][0-9]*$ ]]; then
+  echo "OMP_STREAM_IDLE_TIMEOUT_MS must be a positive integer" >&2
+  exit 2
</file context>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant