{devel}[foss/2022a] PyTorch v1.12.1 w/ Python 3.10.4 (+ CUDA 11.7.0)#16484
Conversation
|
@boegelbot: please test @ generoso |
|
@smoors: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1291050768 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
The test failures are actually expected: PyTorch 1.12 is NOT fully compatible with Python 3.10 yet! This is one of the reasons I was against the new feature of allowing any test to fail only limited by the number of tests. Edit: Will look at the remaining failures later. |
16aedf5 to
dc8d960
Compare
|
@boegelbot: please test @ generoso |
|
@smoors: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1323666191 processed Message to humans: this is just bookkeeping information for me, |
47ed021 to
61bf727
Compare
|
Still working on a test failure which looks real. --> Draft |
|
Test report by @boegelbot |
|
Looks like this is blocked due to a incompatibility with CUDA 11.7 (possibly also 11.6 already): pytorch/pytorch#89684 |
0e8fc9c to
10ac6cd
Compare
|
Test report by @Flamefire |
|
Test report by @Flamefire |
…-1.12.1-foss-2022a.eb and patches: PyTorch-1.12.1_fix-test_wishart_log_prob.patch, PyTorch-1.12.1_python-3.10-annotation-fix.patch, PyTorch-1.12.1_python-3.10-compat.patch, PyTorch-1.12.1_remove-flaky-test-in-testnn.patch
10ac6cd to
544b780
Compare
|
Test report by @branfosj |
|
Going in, thanks @Flamefire! |
|
Test report by @Flamefire |
|
Test report by @boegel |
|
Test report by @boegel |
(created using
eb --new-pr)