Skip to content

remove deprecation warning on get_contiguous_memory_format#37963

Closed
suo wants to merge 1 commit intogh/suo/330/basefrom
gh/suo/330/head
Closed

remove deprecation warning on get_contiguous_memory_format#37963
suo wants to merge 1 commit intogh/suo/330/basefrom
gh/suo/330/head

Conversation

@suo
Copy link
Copy Markdown
Member

@suo suo commented May 6, 2020

Stack from ghstack:

This function is still widely used in the codebase, so we don't want
to add noise to builds with a bunch of warnings. Seems like the
comment + macro are already pretty good indications that this
functionality is considered legacy

Differential Revision: D21434447

This function is still widely used in the codebase, so we don't want
to add noise to builds with a bunch of warnings. Seems like the
comment + macro are already pretty good indications that this
functionality is considered legacy

[ghstack-poisoned]
suo added a commit that referenced this pull request May 6, 2020
This function is still widely used in the codebase, so we don't want
to add noise to builds with a bunch of warnings. Seems like the
comment + macro are already pretty good indications that this
functionality is considered legacy

ghstack-source-id: 11aefbb
Pull Request resolved: #37963
@dr-ci
Copy link
Copy Markdown

dr-ci Bot commented May 6, 2020

💊 Build failures summary and remediations

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


None of the build failures appear to be your fault 💚



🚧 2 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

Since your merge base is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

See how this bot performed.

This comment has been revised 3 times.

@facebook-github-bot
Copy link
Copy Markdown
Contributor

@suo merged this pull request in 4e93844.

@facebook-github-bot
Copy link
Copy Markdown
Contributor

@suo merged this pull request in 4e93844.

1 similar comment
@facebook-github-bot
Copy link
Copy Markdown
Contributor

@suo merged this pull request in 4e93844.

@facebook-github-bot facebook-github-bot deleted the gh/suo/330/head branch May 10, 2020 14:16
hauntsaninja pushed a commit to openai/pytorch that referenced this pull request Nov 3, 2020
…7963)

Summary:
Pull Request resolved: pytorch#37963

This function is still widely used in the codebase, so we don't want
to add noise to builds with a bunch of warnings. Seems like the
comment + macro are already pretty good indications that this
functionality is considered legacy

Test Plan: Imported from OSS

Differential Revision: D21434447

Pulled By: suo

fbshipit-source-id: 08162ed6502894ea5d3ccb92dfa0183232cc2ab5
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 24, 2026
…7963)

Summary:
Pull Request resolved: pytorch#37963

This function is still widely used in the codebase, so we don't want
to add noise to builds with a bunch of warnings. Seems like the
comment + macro are already pretty good indications that this
functionality is considered legacy

Test Plan: Imported from OSS

Differential Revision: D21434447

Pulled By: suo

fbshipit-source-id: 08162ed6502894ea5d3ccb92dfa0183232cc2ab5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants