Skip to content

Conversation

eqy
Copy link
Collaborator

@eqy eqy commented Jul 3, 2024

Found out from #125952 about the existence of _assert_async.

cc @ptrblck @msaroufim

@eqy eqy added module: loss Problem is related to loss function module: cuda Related to torch.cuda, and CUDA support in general open source ciflow/trunk Trigger trunk jobs on your pull request topic: not user facing topic category labels Jul 3, 2024
Copy link

pytorch-bot bot commented Jul 3, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 06ee7ef with merge base a3f3773 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@zou3519 zou3519 added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jul 8, 2024
@eqy
Copy link
Collaborator Author

eqy commented Aug 12, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased graphctc2 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout graphctc2 && git pull --rebase)

@eqy
Copy link
Collaborator Author

eqy commented Aug 27, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased graphctc2 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout graphctc2 && git pull --rebase)

@eqy
Copy link
Collaborator Author

eqy commented Sep 29, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased graphctc2 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout graphctc2 && git pull --rebase)

@eqy
Copy link
Collaborator Author

eqy commented Sep 29, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Tried to rebase and push PR #130071, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

@eqy
Copy link
Collaborator Author

eqy commented Sep 29, 2024

@pytorchmergebot rebase -b main

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased graphctc2 onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout graphctc2 && git pull --rebase)

@eqy
Copy link
Collaborator Author

eqy commented Sep 30, 2024

@pytorchmergebot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@eqy
Copy link
Collaborator Author

eqy commented Sep 30, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Tried to rebase and push PR #130071, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

@eqy
Copy link
Collaborator Author

eqy commented Oct 3, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

eqy and others added 2 commits October 3, 2024 01:14
Co-authored-by: Aaron Gokaslan <aaronGokaslan@gmail.com>
@pytorchmergebot
Copy link
Collaborator

Successfully rebased graphctc2 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout graphctc2 && git pull --rebase)

@eqy
Copy link
Collaborator Author

eqy commented Oct 3, 2024

@pytorchmergebot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

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: cuda Related to torch.cuda, and CUDA support in general module: loss Problem is related to loss function open source topic: not user facing topic category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants