[Klaud Cold] Update gptoss-fp4-h200-trt TRT-LLM image to v1.3.0rc14

[functionstackx]

Summary

Update TensorRT-LLM image from v1.3.0rc11 (34d old) to v1.3.0rc14 (latest pre-release)

• gptoss-fp4-h200-trt: nvcr.io#nvidia/tensorrt-llm/release:1.3.0rc11 → nvcr.io#nvidia/tensorrt-llm/release:1.3.0rc14

Test plan

• full-sweep-enabled sweep passes.

🤖 Generated with Claude Code

[github-actions]

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

• https://docs.sglang.io/cookbook/intro
• https://recipes.vllm.ai/

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

• https://github.com/vllm-project/recipes
• https://github.com/sgl-project/sglang/tree/main/docs_new

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26016889868
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26016889868

[claude]

LGTM — straightforward TRT-LLM image version bump with matching changelog entry.

Extended reasoning...

Overview

This PR updates the TensorRT-LLM container image for the gptoss-fp4-h200-trt config from v1.3.0rc11 to v1.3.0rc14 in .github/configs/nvidia-master.yaml, with a matching entry appended to perf-changelog.yaml.

Security risks

None. This is a YAML configuration change pointing at an official NVIDIA NGC container image (nvcr.io#nvidia/tensorrt-llm/release) — same registry and image family as before, just a newer pre-release tag.

Level of scrutiny

Low. This is a mechanical version bump following the established [Klaud Cold] pattern visible in recent commit history (similar bumps for qwen3.5, kimik2.5, minimaxm2.5). No logic changes, no new code paths, no security-sensitive surfaces touched.

Other factors

The PR carries the full-sweep-enabled label, so the perf sweep CI will validate the new image before merge. The changelog entry correctly references PR #1491 and the config-keys list matches the single key changed. The bug hunting system found no issues.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26016892349
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26016892349

[functionstackx]

Triggered re-run of the failed jobs — the underlying enroot disk issue on h200-nb_0 / h200-nb_1 is being tracked separately in #1496. The h200 SLURM partition tag has been removed from both bad runners, so the re-run should land on the healthy runners only.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26016892349
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26016892349

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26016892349
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26016892349

[functionstackx]

/reuse-sweep-run

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26047488491
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26047488491