-
Notifications
You must be signed in to change notification settings - Fork 704
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
{ai}[foss/2022a] PyTorch v1.13.1 w/ CUDA 11.7.0 #18424
{ai}[foss/2022a] PyTorch v1.13.1 w/ CUDA 11.7.0 #18424
Conversation
…hes: PyTorch-1.7.0_disable-dev-shm-test.patch, PyTorch-1.10.0_fix-kineto-crash.patch, PyTorch-1.11.1_skip-test_init_from_local_shards.patch, PyTorch-1.12.1_add-hypothesis-suppression.patch, PyTorch-1.12.1_fix-skip-decorators.patch, PyTorch-1.12.1_fix-test_cpp_extensions_jit.patch, PyTorch-1.12.1_fix-test_wishart_log_prob.patch, PyTorch-1.12.1_fix-TestTorch.test_to.patch, PyTorch-1.12.1_fix-use-after-free-in-tensorpipe-agent.patch, PyTorch-1.12.1_fix-vsx-loadu.patch, PyTorch-1.12.1_fix-vsx-vector-funcs.patch, PyTorch-1.12.1_skip-test_round_robin.patch, PyTorch-1.13.1_fix-fsdp-fp16-test.patch, PyTorch-1.13.1_fix-kineto-crash-on-exit.patch, PyTorch-1.13.1_fix-pytest-args.patch, PyTorch-1.13.1_fix-test-ops-conf.patch, PyTorch-1.13.1_increase-tolerance-test_ops.patch, PyTorch-1.13.1_increase-tolerance-test_optim.patch, PyTorch-1.13.1_install-vsx-vec-headers.patch, PyTorch-1.13.1_no-cuda-stubs-rpath.patch, PyTorch-1.13.1_remove-flaky-test-in-testnn.patch, PyTorch-1.13.1_skip-failing-grad-test.patch, PyTorch-1.13.1_skip-test-requiring-online-access.patch, PyTorch-1.13.1_skip-tests-without-fbgemm.patch
Since #18421 is a draft, should I assume this is also a draft? Or do you already want me to look at it? |
Test report by @Flamefire |
Yes, this one wasn't supposed to fail, I have to investigate. Might be a patch I missed to include in the PR or so. |
Test report by @Flamefire |
Test report by @Flamefire |
Test report by @Flamefire |
…asyconfigs into 20230731160602_new_pr_PyTorch1131
Test report by @Flamefire |
Test report by @Flamefire |
@boegelbot please test @ generoso |
@casparvl: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1671683983 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
…asyconfigs into 20230731160602_new_pr_PyTorch1131
Test report by @casparvl |
Test report by @Flamefire |
Test report by @branfosj |
@Flamefire Any updates on this? |
Test report by @Flamefire |
@boegel I forgot about this and my (draft) answer is gone. The last run shows 1 failure but the easyblock missed to count it correctly --> easybuilders/easybuild-easyblocks#3003 Also added a patch here and allow some failures to avoid it randomly failing. New reports coming up (3x the same nodes to check for flukes) |
Test report by @branfosj |
Test report by @Flamefire |
Test report by @Flamefire |
Test report by @SebastianAchilles |
Test report by @akesandgren |
@Flamefire Anything more you think need to be done to this? looks good as far as testing goes. |
@akesandgren No it does look good with everything fixed so far. I'm even already using some patches for the 2.x version so yes please get this merged :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Going in, thanks @Flamefire! |
(created using
eb --new-pr
)