💊 CI failures summary and remediations

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

• 1/10 failures possibly* introduced in this PR
  • 1/1 non-scanned failure(s)
• 9/10 broken upstream at merge base f4a5730 on May 12 from 6:49pm to 10:37pm

🚧 9 fixed upstream failures:

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

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

• Linux CI (pytorch-linux-xenial-py3.6-gcc5.4) / test on May 12 from 7:07pm to 7:52pm (f4a5730 - d09abf0)
  • 🔁 rerun
• pytorch_linux_xenial_py3_6_gcc5_4_test on May 12 from 6:49pm to 8:57pm (2279962 - 645a5f7)
  • 🔁 rerun
• pytorch_linux_bionic_py3_8_gcc9_coverage_test1 on May 12 from 6:49pm to 9:18pm (2279962 - f1ac9b6)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cpu_test2 on May 12 from 6:49pm to 8:06pm (2279962 - bc30c31)
  • 🔁 rerun
• pytorch_linux_xenial_py3_clang5_asan_test1 on May 12 from 6:49pm to 9:53pm (2279962 - bc30c31)
  • 🔁 rerun
• pytorch_macos_10_13_py3_test on May 12 from 7:07pm to 9:07pm (f4a5730 - f1ac9b6)
  • 🔁 rerun
• pytorch_linux_bionic_py3_6_clang9_noarch_test on May 12 from 7:07pm to 9:48pm (f4a5730 - 645a5f7)
  • 🔁 rerun
• pytorch_linux_xenial_cuda11_1_cudnn8_py3_gcc7_test1 on May 12 from 6:49pm to 10:34pm (2279962 - 645a5f7)
  • 🔁 rerun
• pytorch_linux_bionic_cuda10_2_cudnn7_py3_9_gcc7_test1 on May 12 from 7:07pm to 10:37pm (f4a5730 - 645a5f7)
  • 🔁 rerun

ci.pytorch.org: 1 failed

• Failed: pr/pytorch-linux-bionic-rocm4.1-py3.6

@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@ngimel merged this pull request in ce3788d.