💊 CircleCI build failures summary and remediations

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

✅ None of the build failures appear to be your fault 💚

• 2/2 broken upstream at merge base 8afa001 since Apr 07

  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.

🚧 2 upstream failures:

These were probably caused by upstream breakages:

• pytorch_bazel_test from Apr 06 until Apr 07 (15 commits; 2e8f954 - ebf743a)
  • 🔁 rerun
• pytorch_cpp_doc_push since Apr 07
  • 🔁 rerun

@xuhdev , there has PR #35092 doing this, in progress of landing. Thanks!

@XiaobingSuper I've resolved conflicts. Please review, thanks!

@xuhdev @XiaobingSuper I'm confused, the previous PR in this stack enables +-/* operations for bfloat16 which are already enabled in one of @XiaobingSuper's PRs? If the previous PR is not actually needed can you close it and have this PR unstacked?

@ngimel The previous PR is a cleanup of the operators -- it did not add the operators

@ngimel merged this pull request in 3a88388.