-
Notifications
You must be signed in to change notification settings - Fork 28
Add CUDA 11.3 and fix broken cuTENSOR variations #658
Conversation
pfnCI, test this please. |
pfnCI, test this please. |
pfnCI, test this please. |
Jenkins CI test (for commit 77a4aee, target branch master) failed with status FAILURE. |
pfnCI, test this please. |
pfnCI, test this please. |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
Blocked by CUDA driver update in Jenkins slave. -> done |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
cupy/cupy#5264 got merged! |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
Hmm there are still some async mempool failures...
|
I could try to take a look later tonight 😅 |
Hmmm I ran |
@leofang Ah yes, several tests may run concurrently on the same device in Jenkins. |
pfnCI, test this please. |
Let's see if cupy/cupy#5308 fixes it...🤞 |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
Well, only part of it...
Let me check later... |
Should we mark these failing tests xfail for the time being? I do not immediately see what else could go wrong and I'm wondering if it's due to architecture difference. |
Agree, sent a PR. cupy/cupy#5350 |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
pfnCI, test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
Jenkins test this please. |
Jenkins CI test (for commit 29b2984, target branch master) failed with status FAILURE. |
Test failure is irrelevant. |
LGTM. |
No description provided.