{ai}[foss/2024a] PyTorch v2.3.0#22616
{ai}[foss/2024a] PyTorch v2.3.0#22616Flamefire wants to merge 7 commits intoeasybuilders:developfrom
Conversation
Updated software
|
|
@Flamefire optree patch is missing from the PR |
6675dc7 to
c624901
Compare
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
@boegelbot please test @ jsc-zen3 |
|
@branfosj: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2798811579 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @branfosj |
|
Test report by @branfosj |
|
Test report by @branfosj |
|
Could I extract optree easyconfig to let my PR work, please? |
|
@branfosj Maybe this can be merged? There is a single failure though. If I could see the logs why |
|
@Flamefire I'm more in favor of going with PyTorch 2.6.0 for |
|
Depends. It might be the smaller barrier to get this in until 2.6/2.7 is ready Also: Shall we continue providing a CPU-only version? The descriptions states "with strong GPU acceleration" which isn't true here. Is anyone using PyTorch without GPUs? |
34a19b7 to
1dd041b
Compare
This reverts commit 1dd041b.
|
PyTorch 2.3 isn't compatible with sympy 1.13 which we already use in 2024a. Maybe pytorch/pytorch#126905 is the upstream PR required but that can't be backported easily. So if we want this, we need to add an exception. Or wait until 2.6 / 2.7 is ready |
|
Test report by @Flamefire |
|
PyTorch 2.6 has been merged: #22824 |
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
Test report by @Flamefire |
(created using
eb --new-pr)