KEMBAR78
[#7288][feat] Added AutoDeploy backend support to test_perf.py by MrGeva · Pull Request #7588 · NVIDIA/TensorRT-LLM · GitHub
Skip to content

Conversation

@MrGeva
Copy link
Collaborator

@MrGeva MrGeva commented Sep 7, 2025

Added support for AD in test_perf.py. for AD it fails the test when perf regression detected. On PT it waives the perf regression as it was done so far - no change for PT test behavior.
Removed the old AD perf test which was disabled anyway, and removed it from the yaml files.

Summary by CodeRabbit

  • New Features
    • Performance tests now support an autodeploy backend, selectable in configs and CLI strings.
    • Added configuration options with defaults: compile backend, free memory ratio, runtime, and an option to skip loading weights.
    • Bench commands and metrics treat autodeploy like PyTorch, skipping build steps and build-time metrics where applicable.
  • Tests
    • Updated parameter parsing and test naming to recognize and display the autodeploy backend.
    • Removed the old AD perf test: trtllm_bench_backend_comparison

Description

Test Coverage

PR Checklist

Please review the following before submitting your PR:

  • PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

  • PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

  • Test cases are provided for new code paths (see test instructions)

  • Any new dependencies have been scanned for license and vulnerabilities

  • CODEOWNERS updated if ownership changes

  • Documentation updated as needed

  • The reviewers assigned automatically/manually are appropriate for the PR.

  • Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md
and the scripts/test_to_stage_mapping.py helper.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

reuse-pipeline

Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 7, 2025

/bot run

@MrGeva MrGeva changed the title Added AD backend support to test_perf.py [#7288][feat] Added AD backend support to test_perf.py Sep 7, 2025
@tensorrt-cicd
Copy link
Collaborator

PR_Github #17921 [ run ] triggered by Bot

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 7, 2025

📝 Walkthrough

Walkthrough

Adds first-class _autodeploy backend support to performance tests: extends PerfTestConfig with four autodeploy options, updates parsing and test naming, adjusts bench command generation to emit extra YAML options for autodeploy, and treats autodeploy like pytorch for build-skipping and metrics (no BUILD_TIME).

Changes

Cohort / File(s) Change Summary
Perf tests config and backend handling
tests/integration/defs/perf/test_perf.py
- Add _autodeploy backend recognition in parsing and naming
- Extend PerfTestConfig.__init__ with ad_compile_backend, free_mem_ratio, extra_runtime, skip_loading_weights
- Update get_trtllm_bench_command to pass --backend=_autodeploy and write extra_llm_api_options YAML with autodeploy config
- Skip build step for _autodeploy like pytorch in get_commands
- Treat _autodeploy like pytorch in metrics: omit BUILD_TIME

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant TR as Test Runner
  participant PC as PerfTestConfig
  participant BC as Bench Cmd Builder
  participant AD as Autodeploy Runtime
  participant MC as Metrics Collector

  TR->>PC: load_from_str(params incl. backend)
  PC-->>TR: PerfTestConfig (incl. autodeploy opts)

  TR->>BC: get_commands(config)
  alt backend == _autodeploy
    BC->>BC: skip build phase
    BC->>BC: write extra_llm_api_options.yaml (compile_backend, free_mem_ratio, runtime, skip_loading_weights)
    BC-->>TR: bench cmd with --backend=_autodeploy and --extra_llm_api_options
  else backend == pytorch
    BC->>BC: skip build phase
    BC-->>TR: bench cmd with --backend=pytorch
  else tensorrt engine
    BC->>BC: include --engine_dir
    BC-->>TR: bench cmd with --backend=tensorrt
  end

  TR->>AD: execute bench command
  AD-->>TR: runtime logs

  TR->>MC: parse logs
  alt backend in {pytorch, _autodeploy}
    MC->>MC: omit BUILD_TIME metric
  else
    MC->>MC: include BUILD_TIME metric
  end
  MC-->>TR: metrics
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • litaotju
  • yilin-void
  • zbpatel
  • StanleySun639

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
tests/integration/defs/perf/test_perf.py (3)

389-394: Consistently namespace new AD params to avoid confusion.

Consider prefixing all AutoDeploy-specific kwargs with ad_ (e.g., ad_free_mem_ratio, ad_runtime, ad_skip_loading_weights) to avoid confusion with existing fields like runtime and kv_cache_free_gpu_mem_fraction. Keeps config surface clear and prevents accidental reuse in other backends.


447-451: Add light validation for new AD fields.

At minimum: assert 0 < free_mem_ratio <= 1 when backend == "_autodeploy". Optional: guard against empty ad_compile_backend and extra_runtime. This prevents silent misconfigurations at collection time.


475-479: Include backend in bench label — OK; optionally add AD knobs when non-default.

Current label adds _autodeploy. Optionally append compact flags (only when diverging from defaults), e.g., ad_cb:torch-opt, ad_rt:trtllm, to disambiguate logs and cache keys. Not strictly required if config files are uniquely named (see next comment).

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aea8ac1 and f5e264a.

📒 Files selected for processing (1)
  • tests/integration/defs/perf/test_perf.py (8 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{h,hpp,hh,hxx,cpp,cxx,cc,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Use only spaces, no tabs; indent with 4 spaces.

Files:

  • tests/integration/defs/perf/test_perf.py
**/*.py

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+.
Indent Python code with 4 spaces; do not use tabs.
Maintain module namespace when importing; prefer 'from package.subpackage import foo' then 'foo.SomeClass()' instead of importing the class directly.
Python filenames should be snake_case (e.g., some_file.py).
Python classes use PascalCase names.
Functions and methods use snake_case names.
Local variables use snake_case; prefix 'k' for variables that start with a number (e.g., k_99th_percentile).
Global variables use upper SNAKE_CASE prefixed with 'G' (e.g., G_MY_GLOBAL).
Constants use upper SNAKE_CASE (e.g., MY_CONSTANT).
Avoid shadowing variables from an outer scope.
Initialize all externally visible members of a class in the constructor.
Prefer docstrings for interfaces that may be used outside a file; comments for in-function or file-local interfaces.
Use Google-style docstrings for classes and functions (Sphinx-parsable).
Document attributes and variables inline so they render under the class/function docstring.
Avoid reflection when a simpler, explicit approach suffices (e.g., avoid dict(**locals()) patterns).
In try/except, catch the most specific exceptions possible.
For duck-typing try/except, keep the try body minimal and use else for the main logic.

Files:

  • tests/integration/defs/perf/test_perf.py
**/*.{cpp,cxx,cc,h,hpp,hh,hxx,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Prepend the NVIDIA Apache-2.0 copyright header with current year to the top of all source files (e.g., .cpp, .h, .cu, .py).

Files:

  • tests/integration/defs/perf/test_perf.py
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Pre-commit Check
🔇 Additional comments (4)
tests/integration/defs/perf/test_perf.py (4)

592-593: Backend parsing updated to recognize “_autodeploy” — looks correct.

No issues spotted in load_from_str; unknown backends still fall back to TensorRT path.


1438-1440: Build skipped for PyTorch and AD backends — consistent with bench semantics.

No action needed.


1692-1695: Skipping builder metrics for PyTorch/AD — matches build-skip behavior.

Log message is clear and backend-aware.


1283-1290: Bench backend switch extended with “_autodeploy” — verify CLI support.

Please confirm trtllm-bench accepts --backend=_autodeploy in this repo/version.

Run:

#!/bin/bash
# Verify backend choices and AD-specific options in the bench CLI.
rg -nP -C3 "(add_argument|ArgumentParser).*--backend" -g '!**/site-packages/**'
rg -n "_autodeploy" -C2
rg -n "extra_llm_api_options" -C3
rg -nP "(compile_backend|free_mem_ratio|skip_loading_weights|runtime)" -C2

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17921 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #13428 completed with status: 'FAILURE'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 7, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17923 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17923 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #13430 completed with status: 'FAILURE'

@MrGeva MrGeva force-pushed the egeva/ad_perf_test branch from d4d5dbd to 9f21c44 Compare September 7, 2025 12:33
@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 7, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17931 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17931 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #13437 completed with status: 'FAILURE'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 7, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17939 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17939 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #13444 completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 8, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17982 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17982 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #13477 completed with status: 'FAILURE'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 8, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18016 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18016 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #13502 completed with status: 'SUCCESS'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 8, 2025

/bot help

@github-actions
Copy link

github-actions bot commented Sep 8, 2025

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

reuse-pipeline

Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 8, 2025

/bot run --stage-list "H100_PCIe-PyTorch-Perf-1" --test-backend "pytorch"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18047 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18047 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #13523 (Partly Tested) completed with status: 'SUCCESS'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 8, 2025

/bot run --disable-reuse-test

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18054 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18054 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #13530 completed with status: 'SUCCESS'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 21, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19435 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19435 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #14604 completed with status: 'SUCCESS'

@github-project-automation github-project-automation bot moved this from Backlog to In review in AutoDeploy Board Sep 25, 2025
Copy link
Collaborator

@omera-nv omera-nv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only reviewed the parts related to testing infra, head two questions

- Added AD backend support in test_perf.py
- Added test to l0_perf.yml with proper configuration
- Updated performance thresholds and regression handling
- Added KV cache metrics and threshold support
- Simplified regex handling for KV cache
- Removed old AD perf test and trtllm_bench_backend_comparison
- Fixed import coding style and various path/param issues

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
@MrGeva MrGeva requested a review from a team as a code owner September 28, 2025 14:33
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 28, 2025

/bot run

@MrGeva MrGeva requested a review from omera-nv September 28, 2025 14:36
@tensorrt-cicd
Copy link
Collaborator

PR_Github #20178 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20178 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #15215 completed with status: 'FAILURE'

@MrGeva
Copy link
Collaborator Author

MrGeva commented Sep 28, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20182 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20182 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #15219 completed with status: 'SUCCESS'

@Fridah-nv Fridah-nv merged commit 9cea6bf into NVIDIA:main Sep 29, 2025
5 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in AutoDeploy Board Sep 29, 2025
MrGeva added a commit that referenced this pull request Oct 2, 2025
… regressions (#8099)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
faradawn pushed a commit to faradawn/TensorRT-LLM that referenced this pull request Oct 2, 2025
…t perf regressions (NVIDIA#8099)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Faradawn Yang <faradawny@gmail.com>
MrGeva added a commit that referenced this pull request Oct 2, 2025
…nd (#8092)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
evezhier pushed a commit to evezhier/TensorRT-LLM that referenced this pull request Oct 3, 2025
…t perf regressions (NVIDIA#8099)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
evezhier pushed a commit to evezhier/TensorRT-LLM that referenced this pull request Oct 3, 2025
… backend (NVIDIA#8092)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
faradawn pushed a commit to faradawn/TensorRT-LLM that referenced this pull request Oct 3, 2025
…t perf regressions (NVIDIA#8099)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Faradawn Yang <faradawny@gmail.com>
faradawn pushed a commit to faradawn/TensorRT-LLM that referenced this pull request Oct 3, 2025
… backend (NVIDIA#8092)

Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Faradawn Yang <faradawny@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

6 participants