Delete Vulkan from code generator.

[ezyang]

Stack from ghstack:

• ATen DerivedType is dead, long live ATen RegisterDispatchKey #47011 ATen DerivedType is dead, long live ATen RegisterDispatchKey
• Convert from higher order functions to classes in tools.codegen.gen #47008 Convert from higher order functions to classes in tools.codegen.gen
• Delete TypeDefault.h and TypeDerived.h codegen entirely. #47002 Delete TypeDefault.h and TypeDerived.h codegen entirely.
• Delete TypeDefault call code generation logic in VariableType #47000 Delete TypeDefault call code generation logic in VariableType
• Delete SchemaRegister.cpp, make flag operate on TypeDefault.cpp #46991 Delete SchemaRegister.cpp, make flag operate on TypeDefault.cpp
• Desugar missing dispatch field into singleton Math entry #46970 Desugar missing dispatch field into singleton Math entry
• Some miscellaneous cleanup in codegen #46940 Some miscellaneous cleanup in codegen
• Delete Vulkan from code generator. #46938 Delete Vulkan from code generator.

It turns out that after #42194
landed we no longer actually generate any registrations into this
file. That means it's completely unnecessary.

Signed-off-by: Edward Z. Yang ezyang@fb.com

Differential Revision: D24573518

[dr-ci]

💊 CI failures summary and remediations

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

---

• 1/2 failures introduced in this PR
• 1/2 broken upstream at merge base c886c7f on Oct 28 from 6:48am to 10:32am PDT (11 commits; 46b252b - 61ee024)

---

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

pytorch_bazel_build (1/1)

Step: "Bazel Build" (full log | diagnosis details | 🔁 rerun)

Oct 28 16:11:22 sccache: error: couldn't connect to server

Oct 28 16:11:22 +++ eval 'extract_trap_cmd ' 
Oct 28 16:11:22 ++++ extract_trap_cmd 
Oct 28 16:11:22 ++++ printf '%s\n' '' 
Oct 28 16:11:22 +++ printf '%s\n' cleanup 
Oct 28 16:11:22 ++ trap -- ' 
Oct 28 16:11:22 cleanup' EXIT 
Oct 28 16:11:22 ++ [[ pytorch-linux-xenial-py3.6-gcc7-bazel-build != *pytorch-win-* ]] 
Oct 28 16:11:22 ++ which sccache 
Oct 28 16:11:22 ++ sccache --stop-server 
Oct 28 16:11:22 Stopping sccache server... 
Oct 28 16:11:22 sccache: error: couldn't connect to server 
Oct 28 16:11:22 sccache: caused by: Connection refused (os error 111) 
Oct 28 16:11:22 ++ true 
Oct 28 16:11:22 ++ rm /var/lib/jenkins/sccache_error.log 
Oct 28 16:11:23 rm: cannot remove '/var/lib/jenkins/sccache_error.log': No such file or directory 
Oct 28 16:11:23 ++ true 
Oct 28 16:11:23 ++ [[ pytorch-linux-xenial-py3.6-gcc7-bazel-build == *rocm* ]] 
Oct 28 16:11:23 ++ SCCACHE_ERROR_LOG=/var/lib/jenkins/sccache_error.log 
Oct 28 16:11:23 ++ SCCACHE_IDLE_TIMEOUT=1200 
Oct 28 16:11:23 ++ RUST_LOG=sccache::server=error 
Oct 28 16:11:23 ++ sccache --start-server 

---

🚧 1 fixed upstream failure:

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

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

If your commit is newer than viable/strict, you can try basing on an older, stable commit:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase --onto FETCH_HEAD $(git merge-base origin/master HEAD)

If your commit is older than viable/strict:

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

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

• pytorch_linux_backward_compatibility_check_test on Oct 28 from 6:48am to 10:32am PDT (11 commits; 46b252b - 61ee024)
  • 🔁 rerun

---

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 or post in the (internal) Dr. CI Users group.

See how this bot performed.

This comment has been revised 12 times.

[facebook-github-bot]

@ezyang merged this pull request in dc6f723.