Skip to content

add the nessesairy constraints for the next 5 benchmarks#82923

Closed
migeed-z wants to merge 8 commits intogh/migeed-z/35/basefrom
gh/migeed-z/35/head
Closed

add the nessesairy constraints for the next 5 benchmarks#82923
migeed-z wants to merge 8 commits intogh/migeed-z/35/basefrom
gh/migeed-z/35/head

Conversation

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 5, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit ad7d549 (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@migeed-z
Copy link
Contributor Author

migeed-z commented Aug 8, 2022

@pytorchbot  merge -g

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 8, 2022

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: argument command: invalid choice: ' merge' (choose from 'merge', 'revert', 'rebase', 'label')

usage: @pytorchbot [-h] {merge,revert,rebase,label} ...

Try @pytorchbot --help for more info.

@migeed-z
Copy link
Contributor Author

@pytorchbot merge -g

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the green (-g) flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@pytorchmergebot
Copy link
Collaborator

Merge failed
Reason: This PR is too stale; the last push date was more than 3 days ago. Please rebase and try again.
Raised by https://github.com/pytorch/pytorch/actions/runs/2871569163

@migeed-z
Copy link
Contributor Author

@pytorchbot merge -g

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the green (-g) flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@github-actions
Copy link
Contributor

Hey @migeed-z.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Aug 17, 2022
…2923)

Summary:
Pull Request resolved: #82923
Approved by: https://github.com/jansel

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/df62ea76d1b443aad8d92b8c6fdad18fae5c6eb6

Reviewed By: seemethere

Differential Revision: D38788361

Pulled By: migeed-z

fbshipit-source-id: f75b3f8853809a3930d976157b0315881740d22a
@facebook-github-bot facebook-github-bot deleted the gh/migeed-z/35/head branch August 20, 2022 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants