-
Notifications
You must be signed in to change notification settings - Fork 23
Investigate failed test on JURECA #38
Comments
Much has changed and much progress has been made with the JURECA implementation; though again we are at a point where one test is failing: Entering
returns
Here I used the "not pcm" flag in the pytest line, because otherwise my PCM (phase-change material) test runs forever until aborting, which unfortunately also kills the pytest execution. The test succeeds on my laptop and on Travis-CI. I have to figure out why the most important test is failing, but it looks like we're on the right track. |
Damian (JURECA support) is helping me debug this issue. |
Damian dug into the build procedure for the FEniCS Docker container and found an important difference that indeed caused the problem. The FEniCS installation on JURECA uses icc and MKL instead of gcc and OpenBLAS (which the FEniCS container uses). Damian re-built FEniCS with gcc and OpenBLAS, and all of my tests now pass. This is not the first time I've encountered finite element software that only works with gcc. deal.II has the same limitation. For the record, here's how I successfully ran the tests:
|
Benedikt built fenics-2017.1.0 (the latest stable version) and installed it in my user home directory; and all but one test passes!
The failed test is "test_ghia1982_steady_lid_driven_cavity_linearized":
bash-4.2$ python -m pytest --cache-show
================================================ test session starts ================================================
platform linux2 -- Python 2.7.13, pytest-3.2.0, py-1.4.34, pluggy-0.4.0
rootdir: /homeb/paj1726/paj17261/fenics/phaseflow-fenics, inifile:
cachedir: /homeb/paj1726/paj17261/fenics/phaseflow-fenics/.cache
--------------------------------------------------- cache values ----------------------------------------------------
cache/lastfailed contains:
{u'tests/test_ghia1982.py::test_ghia1982_steady_lid_driven_cavity_linearized': True}
The other two steady tests pass, and the adaptive space case also uses the linearized form. It is peculiar that this one test fails. Before closing this issue, I should figure out what the relevant differences are between the Docker image's build and our build on JURECA. But for now, I am going to set this aside to focus on writing the proposal, since we have the functionality we need.
The text was updated successfully, but these errors were encountered: