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
{lang}[gfbf/2022b,foss/2022b] SciPy-bundle v2023.02, mpi4py v3.1.4, pybind11 v2.10.3, hypothesis v6.68.2 w/ Python 3.10.8 #16912
{lang}[gfbf/2022b,foss/2022b] SciPy-bundle v2023.02, mpi4py v3.1.4, pybind11 v2.10.3, hypothesis v6.68.2 w/ Python 3.10.8 #16912
Conversation
…hesis v6.59.0 w/ Python 3.10.8
easybuild/easyconfigs/s/SciPy-bundle/SciPy-bundle-2022.11-foss-2022.10.eb
Outdated
Show resolved
Hide resolved
easybuild/easyconfigs/s/SciPy-bundle/SciPy-bundle-2022.11-foss-2022.10.eb
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
…asyconfigs into 20221215150042_new_pr_SciPy-bundle202211
easybuild/easyconfigs/p/pybind11/pybind11-2.10.1-GCCcore-12.2.0.eb
Outdated
Show resolved
Hide resolved
… build dependency + move mpi4py to dedicated easyconfig
Test report by @boegel |
I've converted this back to draft, because it seems like |
easybuild/easyconfigs/s/SciPy-bundle/SciPy-bundle-2022.11-gfbf-2022.10.eb
Outdated
Show resolved
Hide resolved
updated easyblock is in: easybuilders/easybuild-easyblocks#2862 |
Test report by @boegelbot |
Test report by @boegel |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1445181483 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Going in, thanks @boegel! |
Test report by @VRehnberg |
@VRehnberg you need the easyblock from easybuilders/easybuild-easyblocks#2862 |
Test report by @VRehnberg |
Test report by @verdurin |
@boegelbot please test @ generoso |
@jfgrimm: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1463788596 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
@boegelbot please test @ jsc-zen2 |
@branfosj: 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 1463839111 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
With updated easyblocks for me this fails because of missing module "pooch". FAILED ../../linalg/tests/test_decomp.py::TestQZ::test_qz_complex64 - AssertionError: I assume no one uses that at our site so I installed it with --skip-test-step. |
Test report by @3rdcycle |
Not sure how relevant this is given my old CPU architecture (AMD Barcelona). I'm wondering if this is somehow related to #14258 and #11836. The failing tests are different but the assertions occur in connection with longdouble on AMD. What's weird is that when I run some of these tests in isolation, they seem to succeed. E.g.
|
(created using
eb --new-pr
)requires:
update scipy easyblock for scipy >= 1.9 to correctly configure BLAS/LAPACK library to use via Meson (WIP) easybuild-easyblocks#2848or update scipy easyblock for scipy >= 1.9.0 to use meson/ninja easybuild-easyblocks#2862