-
Notifications
You must be signed in to change notification settings - Fork 702
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
{bio,devel}[fosscuda/2019b] PyTorch v1.7.1, typing-extensions v3.7.4.3 w/ Python 3.7.4 #11636
{bio,devel}[fosscuda/2019b] PyTorch v1.7.1, typing-extensions v3.7.4.3 w/ Python 3.7.4 #11636
Conversation
On RHEL8:
Testing if this is fixed by creating and adding libarchive/3.4.2-GCCcore-8.3.0.eb as a build dependency... Yup, that did it. However...
gave me...
Which kinda makes sense? |
Gah, the quantization tests fail again?
|
@terjekv |
…ing-extensions-3.7.4.3-fosscuda-2019b-Python-3.7.4.eb and patches: PyTorch-1.7.0_fix_altivec_defines.patch, PyTorch-1.7.0_fix_test_DistributedDataParallel.patch
939b2a1
to
b7039c3
Compare
Test report by @Flamefire |
Test report by @Flamefire |
Test report by @branfosj |
Test report by @branfosj Error was
I think using |
Test report by @branfosj |
@Flamefire I think that PyTorch v1.7 fits better in |
CUDA 11 is an issue on some sites, e.g. we need some driver update first and IIRC there were some GPUs dropped by CUDA 11 which might be relevant for others. So I'm inclined to keep that in 2019b but add another one to 2020b (I guess as that is the latest), or what would you say? |
Test report by @boegel |
Hmm, still a failing test?
|
This again? See pytorch/pytorch#43209 |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... - notification for comment with ID 756771900 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegel |
Test report by @boegel |
Test report by @boegel |
@Flamefire Installation failed on POWER9, needs the same patch as in #11936?
|
fixed in Flamefire#1 |
add patch for PyTorch 1.7.1 to fix undefined __ieee128 identifier on CentOS 8
Uff, that again... Thanks! |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... - notification for comment with ID 757684698 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot edit: ignore, failed due to lack of disk space... |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... - notification for comment with ID 757998242 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegel |
Test report by @boegel |
Test report by @boegel |
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
)