Conversation
|
Related documentation PR: precice/tutorials#550 |
|
mmh, seems there is still a problem. @MakisH any quick guess? |
You can click on the The issue is independent of the system tests: it's the familiar NumPy 2.0 incompatibility. To fix it, we would need a bugfix release in the tutorials (which I cannot prepare this week). |
I switched to |
MakisH
left a comment
There was a problem hiding this comment.
We still get numpy 2. From the stdout.log of the flow-over-heated-plate OpenFOAM-FEniCS:
#25 [solid-fenics fenics_adapter 3/4] RUN pip3 install --user fenics-ufl
#25 0.911 Collecting fenics-ufl
#25 0.948 Downloading fenics_ufl-2024.1.0.post1-py3-none-any.whl.metadata (2.6 kB)
#25 0.961 Requirement already satisfied: numpy in /home/precice/.local/lib/python3.10/site-packages (from fenics-ufl) (2.0.0)
I can fix all these issues myself, just not right now.
|
After debugging a bit with @fsimonis, we found out that the issue currently is in preCICE, since the migration of the exporters to samples (e414c76). Commit a41d1a2 (one before) does not show the segfault. The issue is not related to Python, as it also happens in OpenFOAM and in the elastic_tube_1d C++. What the failing cases have in common: nearest-neighbor read-consistent mapping and serial-implicit scheme. One case has data initialization, but the other does not. |
|
Another system tests run that reproduces the issue, with debug and trace information.
|
|
We are getting closer: <participant name="Solid">
<provide-mesh name="Solid-Nodes-Mesh" />
<receive-mesh name="Fluid-Nodes-Mesh" from="Fluid" />
<write-data name="CrossSectionLength" mesh="Solid-Nodes-Mesh" />
<read-data name="Pressure" mesh="Solid-Nodes-Mesh" />
<mapping:nearest-neighbor
direction="read"
from="Fluid-Nodes-Mesh"
to="Solid-Nodes-Mesh"
constraint="consistent" />
<export:vtk />
</participant>We assert here: Lines 153 to 154 in 736cbf2 For |
|
self-reminder: Remember to give a green light to the following PRs that will cause some controlled regressions once this is merged: |
|
Current state: all elastic-tube-1d cases show regressions, everything else passes. Plot: Triggered with: gh workflow run run_testsuite_manual.yml -f suites=release_test -f build_args=PLATFORM:ubuntu_2204,PRECICE_REF:7048bd821c23bec44919d9b356cc2293ea0696ab,PRECICE_PRESET:optimized-debug,PYTHON_BINDINGS_REF:v3.1.2,CALCULIX_VERSION:2.20,CALCULIX_ADAPTER_REF:2a5a73a,FENICS_ADAPTER_REF:3de561d,OPENFOAM_EXECUTABLE:openfoam2312,OPENFOAM_ADAPTER_REF:20b4617,SU2_VERSION:7.5.1,SU2_ADAPTER_REF:64d4aff,TUTORIALS_REF:7314ad4 -f systests_branch=develop --ref=develop |
There was a problem hiding this comment.
After several debugging sessions and discussions, I have updated the reference results in precice/tutorials#619 and the tests pass.
I have also fine-tuned several details to make the logs more useful and readable. I think this is now ready to be merged so it does not block other PRs anymore and so that developers can start using it.

Main changes of this PR
Adds a workflow to run the "release" testsuite, which gets triggered by the
trigger-system-testslabel.Motivation and additional information
We have the system tests now. Let's use them.
Author's checklist
pre-commithook to prevent dirty commits and usedpre-commit run --allto format old commits.Reviewers' checklist