-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[https://nvbugs/6655986][test] Raise LTX-2 LPIPS golden thresholds to 0.15 and unwaive #18384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chang-l
wants to merge
1
commit into
NVIDIA:main
Choose a base branch
from
chang-l:fix-ltx2-lpips-threshold-6655986
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2
−4
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: NVIDIA/TensorRT-LLM
Length of output: 1617
🏁 Script executed:
Repository: NVIDIA/TensorRT-LLM
Length of output: 14206
Remove the two obsolete LTX-2 waivers.
tests/integration/test_lists/waives.txtstill skipstest_ltx2_cuda_graph_trtllm_backendandtest_ltx2_example. The backend test usesLTX2_LPIPS_THRESHOLD, so its skip prevents validation of the changed threshold. Keep onlytest_ltx2_feature_accuracy_against_golden[nvfp4]. The affected tests are listed intests/integration/test_lists/test-db/l0_b200.yml.Test coverage summary: no test functions were added, modified, or removed; the changed thresholds are covered by the existing listed tests.
🤖 Prompt for AI Agents
Source: Path instructions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified against current main: the two obsolete NVBug 6655986 waivers remain removed. main has already removed test_ltx2_example, while test_ltx2_cuda_graph_trtllm_backend now has a separate NVBug 6668775 waiver, so that independent waiver must be retained. The signed merge and conflict resolution are ready in companion PR chang-l#7 (commit ffa4f35). @chang-l, please merge #7 into the original head. I am leaving this thread unresolved until #18384 actually contains the update.