Repository navigation
[https://nvbugs/6811958][chore] Unwaive test_build_capture_manifest_matches_committed_golden - #20057
Conversation
|
/bot run |
|
PR_Github #76978 [ run ] triggered by Bot. Commit: |
|
PR_Github #76978 [ run ] completed with state
|
|
/bot run |
|
Heads-up: #20100 adds a new auto-enrolling llm-args field ( |
269cdb6 to
a532821
Compare
|
/bot run |
|
PR_Github #77537 [ run ] triggered by Bot. Commit: |
|
PR_Github #77537 [ run ] completed with state |
|
Follow-up with confirmation: this branch is still based on a pre-#20100 main (CI checks out the PR head directly, so pipeline #63919 is green only because |
a532821 to
67cff13
Compare
|
/bot run |
|
PR_Github #77902 [ run ] triggered by Bot. Commit: |
|
PR_Github #77902 [ run ] completed with state
|
|
/bot run |
|
@farazkh80 Please cherry pick this fix to |
|
PR_Github #77939 [ run ] triggered by Bot. Commit: |
|
PR_Github #77939 [ run ] completed with state
|
|
@QiJune opened #20419 for |
67cff13 to
824306a
Compare
|
/bot run |
|
PR_Github #78188 [ run ] triggered by Bot. Commit: |
…atches_committed_golden Re-enable the premerge privacy gate and regenerate the golden manifest, which drifted again while the waiver hid the test: NVIDIA#20100 added sparse_attention_config.gvr_deterministic_topk to llm_args.py without regenerating. Signed-off-by: Faraz Khoubsirat <58580514+farazkh80@users.noreply.github.com>
824306a to
ab41e80
Compare
|
/bot run |
…atches_committed_golden The golden manifest on release/1.3 is current (regenerated in NVIDIA#19493 via 129655f), so re-enable the premerge privacy gate. Branch-specific counterpart of NVIDIA#20077/NVIDIA#20057 on main. Signed-off-by: Faraz Khoubsirat <58580514+farazkh80@users.noreply.github.com>
|
PR_Github #78222 [ run ] triggered by Bot. Commit: |
|
PR_Github #78188 [ run ] completed with state |
|
PR_Github #78222 [ run ] completed with state
|
|
/bot run |
|
PR_Github #78489 [ run ] triggered by Bot. Commit: |
|
PR_Github #78489 [ run ] completed with state |
Summary
Unwaive
unittest/usage/test_llmapi_config_telemetry_docs.py::test_build_capture_manifest_matches_committed_golden(https://nvbugs/6811958) and regeneratetensorrt_llm/usage/llm_args_golden_manifest.json.The original stale manifest (#19024 added
sparse_attention_config.uses_spcompress) was regenerated in #19493, but the manifest has since drifted again: #19811 changed the capture-policy derivation for nested model-list fields (list[...]wrapper forcuda_graph_config.extra_model_inputs.shape/encoder_cuda_graph_config.extra_model_inputs.shape) without regenerating, and the waiver hid it. Unwaiving without regenerating would re-break the SBSA CPU stage, so both changes are in one commit.Test Coverage
CPU-only, on ToT:
python3 scripts/generate_llm_args_golden_manifest.py→ diff empty after this changepytest tests/unittest/usage/test_llmapi_config_telemetry_docs.py→ 19 passed (fails on the committed manifest with the "manifest is stale" message before this change)pytest tests/unittest/usage/test_llmapi_config_capture.py tests/unittest/usage/test_llmapi_model_sequences.py→ 74 passedCovered in CI by
l0_cpu.yml(unittest/usage).PR Checklist
Dev Engineer Review
TorchLlmArgs.sparse_attention_config.gvr_deterministic_topk.#64214and#64247, but do not identify the failing tests. Their cause and resolution remain unverified.QA Engineer Review
tests/integration/test_lists/waives.txt. It removes the waiver forunittest/usage/test_llmapi_config_telemetry_docs.py::test_build_capture_manifest_matches_committed_golden.tests/integration/test_lists/test-db/l0_cpu.ymllistsunittest/usage.Per-File QA Perspective
tests/integration/test_lists/waives.txt: Removing the waiver enables the golden-manifest check to run. The test is underunittest/usage, whichl0_cpu.ymllists.tensorrt_llm/usage/llm_args_golden_manifest.json: The change summary reports the addition of the booleansparse_attention_config.gvr_deterministic_topkentry. Verify the committed manifest matches the generator on the target branch.