🐛 [Bug] Weight streaming test failures
Open
Nobody has claimed this yet.
bug
Story: Runtime & Memory & Serialization
- Dominant language
- Python
- Stars
- 3k
- Forks
- 410
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 78
Description
Bug Description
FAILED runtime/test_004_weight_streaming.py::TestWeightStreamingPython::test_weight_streaming_default_0_python_runtime - AssertionError: Tensor-likes are not close!
FAILED runtime/test_004_weight_streaming.py::TestWeightStreamingPython::test_weight_streaming_default_1_cpp_runtime - AssertionError: Tensor-likes are not close!
FAILED runtime/test_004_weight_streaming.py::TestWeightStreamingPython::test_weight_streaming_manual_0_python_runtime - AssertionError: Tensor-likes are not close!
FAILED runtime/test_004_weight_streaming.py::TestWeightStreamingPython::test_weight_streaming_manual_1_cpp_runtime - AssertionError: Tensor-likes are not close!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Environment
Build information about Torch-TensorRT can be found by turning on debug messages
- Torch-TensorRT Version (e.g. 1.0.0):
- PyTorch Version (e.g. 1.0):
- CPU Architecture:
- OS (e.g., Linux):
- How you installed PyTorch (
conda,pip,libtorch, source): - Build command you used (if compiling from source):
- Are you using local sources or building from archives:
- Python version:
- CUDA version:
- GPU models and configuration:
- Any other relevant information:
Additional context
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.
Research direction
Start with the four failing tests in runtime/test_004_weight_streaming.py and run the listed Python- and C++-runtime cases to reproduce the tensor comparison failures. Trace the weight-streaming behavior involved in those tests and verify that all four tests pass with matching tensors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- machine-learning, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100