Repository navigation
[https://nvbugs/7042835][test] Unwaive unittest/disaggregated fixed by #21597 - #21810
Conversation
…NVIDIA#21597 NVIDIA#21021 renamed KVCacheManagerV2.low_precision_dtype, but the BF16 context-first profile check still read the old name, so unittest/disaggregated failed in the CPU stage and the whole directory was waived. NVIDIA#21597 fixed that reader. Remove the directory waive. Signed-off-by: tianruih <tianruih@nvidia.com>
|
/bot run --disable-fail-fast |
|
No actionable comments were generated in the recent review. WalkthroughThe integration test waiver list no longer includes the ChangesIntegration test waivers
Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Suggested reviewers: Merge Risk:
|
|
PR_Github #83115 [ run ] triggered by Bot. Commit: |
|
PR_Github #83115 [ run ] completed with state |
sunnyqgg
left a comment
There was a problem hiding this comment.
Reviewed the one-line unwaive of unittest/disaggregated (nvbugs/7042835): 0 Blocker, 0 Possibly blocking, 1 Required, 0 Nice to have. The fix (#21597) is on the base, and all 42 sub-test failures behind the waive (pre-merge 68002) were the renamed low_precision_dtype reader. This PR's pre-merge run (L0_MergeRequest_PR 68667) ran test_unittests_v2[unittest/disaggregated] unwaived on CPU-Generic-x86-1 and CPU-Generic-arm-1: 1795 passed, 2 strict xfail, 0 failed. Waives match exact node ids, so this line only ever skipped the l0_cpu directory entry, and no GPU stage is affected.
- [Required] The same root cause also left three DGX_H100 waives on main, and this unwaive should take them with it. After this PR's base, #21730 added
full:DGX_H100/unittest/disaggregated/test_kv_transfer_mp.py::test_context_first_bf16_owned_transfer,full:DGX_H100/unittest/disaggregated/test_transfer_lifecycle_gpu.py::test_context_first_bf16_lifecycle_gpuandfull:DGX_H100/disaggregated/test_disaggregated.py::test_disaggregated_context_first_bf16_ownershipunder nvbugs/7051902 (waives.txt:93, 95 and 96 on main). In post-merge 3055 (2a8d8e4, before #21597),test_context_first_bf16_owned_transfer[tp1/tp2]failed atand manager.low_precision_dtype is NonewithAttributeError: 'KVCacheManagerV2' object has no attribute 'low_precision_dtype', the same failure as 7042835. In post-merge 3057 (d782229, which includes #21597 and predates the waive), all three passed on DGX_H100-4_GPUs-PyTorch-Others-1/2. As it stands, the 4-GPU context-first BF16 transfer path stays skipped on DGX_H100 even though it is fixed, and 7051902 has no engineer assigned. Please rebase and drop those three lines here, confirmed with/bot run --stage-list "DGX_H100-4_GPUs-PyTorch-Others-1,DGX_H100-4_GPUs-PyTorch-Others-2", and close 7051902 as a duplicate of 7042835. If you'd rather do it in a follow-up, link 7051902 from this PR.
|
Automatically added "ci: full pre-merge approved" because this PR has satisfied the required GitHub review approvals. Unresolved review conversations and other required checks remain independent merge requirements. |
Brings the branch up to date with main. main removed the waive of unittest/disaggregated (NVIDIA#21810) after NVIDIA#21597 fixed those tests, so the pre-merge CPU stage now runs the tests in tests/unittest/disaggregated, including the ones this branch adds. No conflicts. Signed-off-by: berryz <berryz@nvidia.com>
…ordinator socket test main removed the unittest/disaggregated waiver (NVIDIA#21810), so that entry runs test_coordinator_uds.py again. The separate entry would run the file's five cases a second time. Signed-off-by: berryz <berryz@nvidia.com>
Description
#21021 renamed
KVCacheManagerV2.low_precision_dtype, but the BF16 context-first profile check still read the old name, sounittest/disaggregatedfailed in the CPU stage (https://nvbugs/7042835) and the whole directory was waived. #21597 fixed that reader. This PR removes the directory waive.Test Coverage
unittest/disaggregatedin the CPU stage (l0_cpu.yml), the only stage that runs the directory as a whole.Dev Engineer Review
The PR removes the blanket
unittest/disaggregatedwaiver for NVBUG 7042835 fromtests/integration/test_lists/waives.txt. Theunittest/disaggregatedsuite remains listed in the CPU test configuration. The change removes the skip; it does not change test code or establish that the tests pass.QA Engineer Review
The PR modifies one test-list file and removes one directory-wide waiver. The CPU test list still includes
unittest/disaggregated, so those tests can run without the blanket skip. The supplied evidence does not include completed test results. Coverage verdict: needs follow-up.Per-File QA Perspective
tests/integration/test_lists/waives.txt: Removes the waiver forunittest/disaggregated. Verify that the CPU-stage suite runs as intended after removal.