💊 CircleCI build failures summary and remediations

As of commit 100fb6d:

None of the build failures appear to be your fault.

• 2/2 broken upstream at merge base 9e9bfbf since Jan 02

  You may want to 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 origin viable/strict
  git rebase --onto viable/strict $(git merge-base origin/master HEAD)
  

  If your commit is older than viable/strict:

  git fetch origin viable/strict
  git rebase viable/strict
  

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

Detailed failure analysis

One may explore the probable reasons each build failed interactively on the Dr. CI website.

🚧 2 upstream failures recognized by patterns:

These builds matched patterns, but were probably caused by upstream breakages:

• pytorch_linux_backward_compatibility_check_test from Jan 02 until Jan 02
• pytorch_macos_10_13_py3_test from Jan 02

@seemethere what is this for? I thought the next version should be 1.4.0. am i missing anything here?

I believe @ezyang had mentioned that we should update these to 1.5.0

There are a lot of duplicated version numbers in the ios packaging, @xta0 it would be good to figure out how to reduce this number as much as possible

@ezyang I think there is just one file in this PR that related to iOS. Where are the other duplicated version numbers?

@seemethere merged this pull request in 346a349.