Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

ezyang
Copy link
Contributor

@ezyang ezyang commented Mar 25, 2024

Stack from ghstack (oldest at bottom):

Signed-off-by: Edward Z. Yang [email protected]

cc @albanD

[ghstack-poisoned]
@ezyang ezyang requested a review from ejguan as a code owner March 25, 2024 16:41
Copy link

pytorch-bot bot commented Mar 25, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/122616

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 2 Unrelated Failures

As of commit dce7bc2 with merge base failed to retrieve merge base, please contact dev infra:

NEW FAILURE - The following job has failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the release notes: dataloader release notes category label Mar 25, 2024
@ezyang ezyang requested review from peterbell10 and removed request for SherlockNoMad, albanD, antoniojkim, bdhirsh and miladm March 25, 2024 16:41
@ezyang ezyang added ciflow/trunk Trigger trunk jobs on your pull request topic: bug fixes topic category module: python frontend For issues relating to PyTorch's Python frontend labels Mar 25, 2024
[ghstack-poisoned]
ezyang added a commit that referenced this pull request Mar 25, 2024
Signed-off-by: Edward Z. Yang <[email protected]>

ghstack-source-id: d3c295c
Pull Request resolved: #122616
@ezyang
Copy link
Contributor Author

ezyang commented Mar 25, 2024

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: pull / before-test / llm-retrieval, trunk / before-test / llm-retrieval

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@ezyang
Copy link
Contributor Author

ezyang commented Mar 26, 2024

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 3 checks: .github/workflows/pull.yml / before-test / llm-retrieval, .github/workflows/pull.yml / linux-focal-py3_8-clang9-xla / test (xla, 1, 1, linux.12xlarge), .github/workflows/trunk.yml / before-test / llm-retrieval

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@peterbell10
Copy link
Collaborator

@pytorchbot merge -f "Unrelated failure"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

pytorch-bot bot pushed a commit that referenced this pull request Apr 22, 2024
@malfet malfet added this to the 2.3.1 milestone Apr 25, 2024
@Rhett-Ying
Copy link

Is there any workaround for this issue if working with torch 2.3.0?

@albanD
Copy link
Collaborator

albanD commented May 8, 2024

I would expect that you can work around this by doing the imports this way, not ideal though:

import torch
torch.utils.data.datapipes.utils.common.DILL_AVAILABLE = torch.utils._import_utils.dill_available()
import torchdata

@Atul-1992
Copy link

Thanks, It worked!

@atalman
Copy link
Contributor

atalman commented May 13, 2024

@pytorchbot cherry-pick --onto release/2.3 -c regression --fixes #124907

pytorchbot pushed a commit that referenced this pull request May 13, 2024
Signed-off-by: Edward Z. Yang <[email protected]>

Pull Request resolved: #122616
Approved by: https://github.com/peterbell10

(cherry picked from commit f428183)
@pytorchbot
Copy link
Collaborator

Cherry picking #122616

The cherry pick PR is at #126094 and it is linked with issue #124907

Details for Dev Infra team Raised by workflow job

huydhn pushed a commit that referenced this pull request May 13, 2024
Restore DILL_AVAILABLE for backwards compat with torchdata (#122616)

Signed-off-by: Edward Z. Yang <[email protected]>

Pull Request resolved: #122616
Approved by: https://github.com/peterbell10

(cherry picked from commit f428183)

Co-authored-by: Edward Z. Yang <[email protected]>
@sarikasaxena30
Copy link

FileNotFoundError: Cannot find DGL C++ graphbolt library at /usr/local/lib/python3.10/dist-packages/dgl/graphbolt/libgraphbolt_pytorch_2.3.0.so
How to solve this problem?anyone can help me in this

@github-actions github-actions bot deleted the gh/ezyang/2633/head branch July 7, 2024 01:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged module: python frontend For issues relating to PyTorch's Python frontend release notes: dataloader release notes category topic: bug fixes topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants