Conversation
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com>
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com>
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
|
[🤖]: Hi @chtruong814 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully. So it might be time to merge this PR or get some approvals. |
|
[🤖]: Hi @chtruong814 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully. So it might be time to merge this PR or get some approvals. |
| # Newer versions of torch.utils.data.Sampler do not have the data_source parameter. | ||
| # lhotse's CutSampler expects to pass data_source to Sampler, so we need to patch | ||
| # Sampler.__init__ to accept it. | ||
| if "data_source" not in inspect.signature(Sampler.__init__).parameters: | ||
|
|
||
| def patched_sampler_init(self, data_source=None): | ||
| pass | ||
|
|
||
| Sampler.__init__ = patched_sampler_init |
There was a problem hiding this comment.
@chtruong814 How urgent is it to merge this PR? I can release a new lhotse version tested against latest pytorch so that this patch is not needed.
There was a problem hiding this comment.
We're going to build a container release candidate at end of Monday. Do you think we can do that before then? If not, we can merge this and then remove when the updated lhotse is ready?
There was a problem hiding this comment.
OK if it passes all tests, let's do it and remove later.
Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com>
|
[🤖]: Hi @chtruong814 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully. So it might be time to merge this PR or get some approvals. |
* Bump to pytorch 25.11 Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Patch torch Sampler to expect data_source param for lhotse Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Apply isort and black reformatting Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com> * Skip broken asr onnx tests due to pytorch 25.11 update Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Apply isort and black reformatting Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com> * Only run speech tests for now Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Fix speech CI Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Revert "Fix speech CI" This reverts commit 8acdc2b. Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Revert "Only run speech tests for now" This reverts commit bb3412e. Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Revert "Apply isort and black reformatting" This reverts commit 73b79f3. Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Revert "Skip broken asr onnx tests due to pytorch 25.11 update" This reverts commit 8710db3. Signed-off-by: Charlie Truong <chtruong@nvidia.com> * Apply isort and black reformatting Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com> --------- Signed-off-by: Charlie Truong <chtruong@nvidia.com> Signed-off-by: chtruong814 <chtruong814@users.noreply.github.com> Co-authored-by: chtruong814 <chtruong814@users.noreply.github.com> Signed-off-by: Akhil Varanasi <akhilvaranasi23@gmail.com>
What does this PR do ?
Bump to pytorch 25.11
Collection: [Note which collection this PR will affect]
Changelog
Usage
# Add a code snippet demonstrating how to use thisGitHub Actions CI
The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.
The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".
Before your PR is "Ready for review"
Pre checks:
PR Type:
If you haven't finished some of the above items you can still open "Draft" PR.
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information