-
Notifications
You must be signed in to change notification settings - Fork 22.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parametrizations depending on several inputs #60530
Conversation
Better testing Better docs
Use collections.abc Change the handling of a sequence of one tensor Reword some bits
💊 CI failures summary and remediationsAs of commit bca087e (more details on the Dr. CI page and at hud.pytorch.org/pr/60530):
🕵️ 2 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages: pytorch_paralleltbb_linux_xenial_py3_6_gcc5_4_test (1/2)Step: "Run tests" (full log | diagnosis details | 🔁 rerun)
|
Job | Step | Action |
---|---|---|
binary_linux_libtorch_3_7m_cpu_gcc5_4_cxx11-abi_shared-with-deps_test | Run in docker | 🔁 rerun |
3 jobs timed out:
binary_linux_libtorch_3_7m_cpu_gcc5_4_cxx11-abi_shared-with-deps_test
pytorch_libtorch_linux_xenial_cuda11_1_cudnn8_py3_gcc7_build
pytorch_libtorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_build
🚧 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 older than viable/strict
, run these commands:
git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD
- pytorch_libtorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_build from Jun 21 until Jun 23 (5d476f5 - 63219f1)
ci.pytorch.org: 1 failed
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 to the (internal) Dr. CI Users group.
Thanks! |
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Summary: Resubmit of pytorch#58488 There was a line that had been changed in `test_nn.py` as caught in pytorch#58488 (comment) I reverted that line, which should never have been changed. I reckon that should solve the issue. Pull Request resolved: pytorch#60530 Reviewed By: ngimel Differential Revision: D29329865 Pulled By: albanD fbshipit-source-id: 8dfd0cd968fe26a3924dae7ca366af2c8a8639b3
Summary: Resubmit of #58488 There was a line that had been changed in `test_nn.py` as caught in #58488 (comment) I reverted that line, which should never have been changed. I reckon that should solve the issue. Pull Request resolved: #60530 Reviewed By: ngimel Differential Revision: D29329865 Pulled By: albanD fbshipit-source-id: 8dfd0cd968fe26a3924dae7ca366af2c8a8639b3
Resubmit of #58488
There was a line that had been changed in
test_nn.py
as caught in #58488 (comment)I reverted that line, which should never have been changed. I reckon that should solve the issue.