Skip to content

Conversation

@malfet
Copy link
Contributor

@malfet malfet commented Apr 1, 2022

Stack from ghstack:

It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 1, 2022

🔗 Helpful links

💊 CI failures summary and remediations

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


💚 💚 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.

malfet added a commit that referenced this pull request Apr 1, 2022
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

ghstack-source-id: 70e3ddd
Pull Request resolved: #75085
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

[ghstack-poisoned]
malfet added a commit that referenced this pull request Apr 2, 2022
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

ghstack-source-id: 8db31ff
Pull Request resolved: #75085
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

[ghstack-poisoned]
malfet added a commit that referenced this pull request Apr 5, 2022
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

ghstack-source-id: 14889fa
Pull Request resolved: #75085
@malfet
Copy link
Contributor Author

malfet commented Apr 5, 2022

@pytorchbot merge this

@github-actions
Copy link
Contributor

github-actions bot commented Apr 5, 2022

Hey @malfet.
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 Apr 7, 2022
Summary:
It caused a number of internal only compilation failures, for example
see:
#74425 (comment)
and #74542 (comment)

Pull Request resolved: #75085

Approved by: https://github.com/ngimel, https://github.com/albanD

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

Reviewed By: b0noI

Differential Revision: D35404322

Pulled By: malfet

fbshipit-source-id: aaa7033d0b7cbfcc1d4b3eeff86d09eba428f068
@facebook-github-bot facebook-github-bot deleted the gh/malfet/49/head branch April 8, 2022 23:01
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.

5 participants