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 v2.1.2 #19444
{ai}[foss/2022a] PyTorch v2.1.2 #19444
Conversation
…2.0.1_avoid-test_quantization-failures.patch, PyTorch-2.0.1_fix-skip-decorators.patch, PyTorch-2.0.1_fix-ub-in-inductor-codegen.patch, PyTorch-2.0.1_fix-vsx-loadu.patch, PyTorch-2.0.1_no-cuda-stubs-rpath.patch, PyTorch-2.0.1_skip-failing-gradtest.patch, PyTorch-2.0.1_skip-test_shuffle_reproducibility.patch, PyTorch-2.0.1_skip-tests-skipped-in-subprocess.patch, PyTorch-2.1.0_fix-bufferoverflow-in-oneDNN.patch, PyTorch-2.1.0_fix-validationError-output-test.patch, PyTorch-2.1.0_fix-vsx-vector-shift-functions.patch, PyTorch-2.1.0_increase-tolerance-functorch-test_vmapvjpvjp.patch, PyTorch-2.1.0_remove-sparse-csr-nnz-overflow-test.patch, PyTorch-2.1.0_remove-test-requiring-online-access.patch, PyTorch-2.1.0_skip-diff-test-on-ppc.patch, PyTorch-2.1.0_skip-dynamo-test_predispatch.patch, PyTorch-2.1.0_skip-test_jvp_linalg_det_singular.patch, PyTorch-2.1.0_skip-test_linear_fp32-without-MKL.patch, PyTorch-2.1.0_skip-test_wrap_bad.patch
Test report by @Flamefire |
Test report by @Flamefire |
Test report by @casparvl |
@casparvl I assume the failures are the same as in #19445 (comment) ? Except for test_sympy_utils which requires rebuilding #19414 Do you see the same failures in #19086 / #19087 or are those test_jit failures new in 2.1.2? |
Marking this as ready as it doesn't seem to fail more than 2.1.0 so this might be better than #19086 |
@boegelbot please test @ generoso |
@SebastianAchilles: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1867587873 processed Message to humans: this is just bookkeeping information for me, |
Yeah, sorry, little time to follow up from my side. Test failures where indeed the same, except the I'll try to upload a test report for #19086 and #19087. I'll be going on holiday after today, so I'll just turn on those builds, and hope for the best... I'm afraid I can't look into the build failures and report more specifically then, but at least you should be able to see the summary of failures in the gist. |
Test report by @SebastianAchilles |
@boegelbot please test @ jsc-zen2 |
@SebastianAchilles: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1867921830 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @boegelbot |
Test report by @bedroge |
Test report by @SebastianAchilles |
Test report by @SebastianAchilles |
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! |
legend 🎉 |
(created using
eb --new-pr
)Update over #19086
test_sympy_utils
failure requires rebuilding with #19414