You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG]: nv_build with no llm-model returns HTTP 404 for our NVIDIA Build key, so RUBRIC_EVAL and the LLM security verification do not run #510
Thank you for the reusable workflow and the nv_build provider; with a model named, the LLM checks ran well for us.
ci/README.md at v0.9.0 says llm-model is optional. With llm-provider: nv_build and llm-model left empty, the run uses the default from src/skillevaluator/provider_config.py (CHAT_DEFAULT_NVIDIA = "nvidia/nemotron-3-super-120b-a12b", line 52 at v0.9.0). For our NVIDIA Build key that model answers HTTP 404, so RUBRIC_EVAL fails without running ("LLM judge unavailable; rubric evaluation did not run") and the security scan lists llm-verification as incomplete. The message the run printed was: "Model or endpoint unavailable. Check SKILL_EVAL_LLM_MODEL against the provider's available models."
Expected: the default nv_build model is callable with an NVIDIA Build key, or the run says the default model itself is unavailable and suggests setting llm-model.
Actual: a 404 that reads like a setup mistake on our side, with no model named by us.
What we checked outside the workflow, with the same account's key, one 4-token call per model on https://integrate.api.nvidia.com/v1:
GET /models lists nvidia/nemotron-3-super-120b-a12b.
POST /chat/completions with that model: HTTP 404, "Function '…': Not found for account '…'" (ids left out here).
nvidia/nemotron-3-ultra-550b-a55b, nvidia/nemotron-3.5-lightning-30b-a3b and nvidia/nemotron-3-nano-omni-30b-a3b-reasoning: HTTP 200.
So the model is listed but not callable on our account. We have one account to test with and cannot tell whether this is specific to it or to free NVIDIA Build accounts in general.
Possible directions, offered, not prescribed: a default model that NVIDIA Build serves to every key; or, on a 404 from the default model, a message that names the default and suggests llm-model; or a line in ci/README.md that the default may not be callable on every account.
Reproduction steps
In a public repository with one skill under skills/, add ci/bundles/0.9.0/skill-checks-llm.yml from the v0.9.0 tag with llm-provider: nv_build and llm-model empty, and an NVIDIA Build key in the secret LLM_API_KEY.
Run it. RUBRIC_EVAL fails with the 404 above.
Set llm-model: nvidia/nemotron-3-ultra-550b-a55b and run again: the rubric and the LLM verification run.
One more data point, which may explain the 404: the model's page on NVIDIA Build, https://build.nvidia.com/nvidia/nemotron-3-super-120b-a12b, read today (2026-11-14), lists its availability as "Free Endpoint: Deprecated", "Partner Endpoint: Available" and "Download: Available". So the nv_build default looks like a model whose free hosted endpoint has been retired, which would affect every key that relies on the free endpoint, not only ours. We have not seen a date for the change.
Thanks for the detailed report and the model-by-model check, that made this easy to pin down.
Fix is up in #514. On a 404 the message now says the provider's default model may not be callable with your key and points to llm-model (SKILL_EVAL_LLM_MODEL outside CI). ci/README.md says the same. The default model itself is unchanged for now; whether to move it to one every NVIDIA Build key can call is a separate call we'll look at.
Once #514 is merged, could you re-run with an empty llm-model and confirm the new message reads right? We'll leave this open until you do.
Re-ran it with main at a8436f6 (which has #514), locally, since our CI pins the v0.9.0 image: tier1 on TheColliery/CoalFace's skill with nv_build and no model set, our NVIDIA Build key. The new message reads right:
LLM judge unavailable; rubric evaluation did not run: HTTP 404: Model or endpoint unavailable. If no model was set, the provider's default may not be callable with this key; set SKILL_EVAL_LLM_MODEL (llm-model in CI) to a model the key can use.
It names the cause and the setting, so a reader knows what to do. One small thing, offered only: the finding's Fix: line still says "Configure a public LLM provider to enable LLM rubric evaluation", which points at the provider when the provider is set and only the default model is unreachable. Naming llm-model there too would make the two lines agree. Fine to close from our side either way.
Activity
HetCreep commentedon Nov 13, 2026
One more data point, which may explain the 404: the model's page on NVIDIA Build, https://build.nvidia.com/nvidia/nemotron-3-super-120b-a12b, read today (2026-11-14), lists its availability as "Free Endpoint: Deprecated", "Partner Endpoint: Available" and "Download: Available". So the
nv_builddefault looks like a model whose free hosted endpoint has been retired, which would affect every key that relies on the free endpoint, not only ours. We have not seen a date for the change.chrisknvidia commentedon Nov 13, 2026
Thanks for the detailed report and the model-by-model check, that made this easy to pin down.
Fix is up in #514. On a 404 the message now says the provider's default model may not be callable with your key and points to
llm-model(SKILL_EVAL_LLM_MODELoutside CI).ci/README.mdsays the same. The default model itself is unchanged for now; whether to move it to one every NVIDIA Build key can call is a separate call we'll look at.Once #514 is merged, could you re-run with an empty
llm-modeland confirm the new message reads right? We'll leave this open until you do.HetCreep commentedon Nov 14, 2026
Re-ran it with
mainata8436f6(which has #514), locally, since our CI pins thev0.9.0image:tier1onTheColliery/CoalFace's skill withnv_buildand no model set, our NVIDIA Build key. The new message reads right:It names the cause and the setting, so a reader knows what to do. One small thing, offered only: the finding's
Fix:line still says "Configure a public LLM provider to enable LLM rubric evaluation", which points at the provider when the provider is set and only the default model is unreachable. Namingllm-modelthere too would make the two lines agree. Fine to close from our side either way.