{data}[gompi/2022.10] netCDF-Fortran v4.6.0, netCDF v4.9.0, HDF5 v1.12.2, Szip v2.1.1#16834
{data}[gompi/2022.10] netCDF-Fortran v4.6.0, netCDF v4.9.0, HDF5 v1.12.2, Szip v2.1.1#16834boegel wants to merge 4 commits intoeasybuilders:developfrom
Conversation
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1342538205 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
…asyconfigs into 20221208120057_new_pr_netCDF-Fortran460
|
Test report by @branfosj |
|
Test report by @branfosj |
|
@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)... Details- notification for comment with ID 1343226691 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Same test fails on both In the past it seems like this was a sign of a bug in Open MPI, see Unidata/netcdf-c#1500. |
|
@boegelbot please test @ generoso |
|
@branfosj: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1344306828 processed Message to humans: this is just bookkeeping information for me, |
|
We disabled one of the parts of |
|
Test report by @boegelbot |
|
@branfosj How do you think we should proceed here? Extend the timeout? |
We should try with a longer timeout - to see how long it takes for these tests to complete. I expect that we'll just keep increasing it for the tests in here - I supsect that the functionality these tests hit are a bad fit for certain types of filesystems. |
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1360078495 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegel |
…on some types of filesystems
18fa679 to
d721297
Compare
|
I have cancelled job Instead, I've added a new patch in d721297 which disable one more test, because it's running excessively long on some types of filesystems. |
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 1361001272 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @boegel |
| and machine-independent data formats that support the creation, access, and sharing of array-oriented | ||
| scientific data.""" | ||
|
|
||
| toolchain = {'name': 'gompi', 'version': '2022.10'} |
There was a problem hiding this comment.
Note: version should be updated to 2022b once #16961 is merged
|
I am also seeing the timeout on my system. In my case I am running the test report in a container and the filesystem is mounted into the container, e.g. similar to:
I tried to nail down the tests that are talking so long. To get rid of the timeout I had to disable in addition to the already disabled tests the Skipping these tests also works on |
|
I would have thought the It did fix things for the person who originated this issue a while back #15959 If it's not enough, then we should apply this new patch to those easyconfigs as well. |
|
Yes, in the 2022a toolchain skipping only the |
|
So the difference stems from the compiler and MPI change, or the version bump of libxml2 and cURL. Maybe it's not so clear cut that these failures should just be ignored? I'll try on cephfs, to see if that also has problems without these patches (it never had issues with any of the tests before). |
(created using
eb --new-pr)requires: