aste-turbine runs are non-reproducible

Running the aste-turbine tutorial multiple times (with export:vtu enabled), I get different export files in each run. Example from four consecutive runs:

precice-export.tar.gz

It looks like the directories include files that have the same name but correspond to different parts of the domain. See, for example: debug.tar.gz

I am using ASTE from the latest develop. This includes a commit which was addressing a similar problem.

To reproduce, set <export:vtu directory="precice-exports" /> in both participants in the precice-config.xml: precice-config.xml

Dockerfile to reproduce: Dockerfile.txt

mv Dockerfile.txt Dockerfile
docker buildx build -t test-aste .
cd tutorials/
docker run -it --mount type=bind,src=.,dst=/mnt/host test-aste:latest

and inside the container:

source ~/venv/bin/activate
cd /mnt/host/aste-turbine
./run.sh
cp -r precice-exports/ precice-exports-run1/
./run.sh
cp -r precice-exports/ precice-exports-run2/

Then, compare the respective files with a diff tool or fieldcompare.

Observed in the context of #876. Comparing these otherwise unrelated files will also give some errors in fieldcompare (see related issue).

Start with tutorials/aste-turbine/run.sh and the precice-config.xml used by both participants, then reproduce the two runs with the provided Dockerfile.txt and compare precice-exports-run1/ and precice-exports-run2/. Check the linked ASTE commit and related context from #876. Done means repeated export:vtu runs produce matching files, or the responsible component is identified clearly.