[Feature]: AutoDeploy: unit testing with node+arg counting
@2ez4bz is already working on this.
Since Dec 2, 2025.
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
🚀 The feature, motivation and pitch
From time to time, we exhibit regressions related to certain transforms causing e2e failures/regressions. This can be caused by changes in other transforms or mishandling of corner cases.
A recent example of this is https://github.com/NVIDIA/TensorRT-LLM/issues/8389
This can have downstream issues for both accuracy and performances.
This ticket is tracking adding a new type of unit/e2e test to track such potential regressions. The idea is to build test infrastructure where we do "node counting" on the final graph. More specifically, we can do the following:
- Run an e2e test like
test_ad_build_and_run_single.py - Check out the graph in the final stages of the transform pipeline
- Do some basic graph analysis on the final graph such as
a. How many nodes of each type?
b. How many function calls for each op?
c. Check if important arguments are correct
d. Analyze resulting shapes of fake tensors from shape prop
e. ....
Alternatives
No response
Additional context
No response
Before submitting a new issue...
- Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.