You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The tpv5-poro test fails from time to time in the CI due to a segfault. If it happens, it always does so about 30 seconds into the run. Given that the successful runtime is about 2 min 30 s, and the run taking pretty exactly 2 mins, I'd suspect that it happens in one of the first iterations.
Expected behavior
The test should pass consistently.
To Reproduce
Steps to reproduce the behavior: submit a CI job several times (e.g. create any new branch, or commit to an existing one), eventually one of them will fail at tpv5-poro.
Describe the bug
The tpv5-poro test fails from time to time in the CI due to a segfault. If it happens, it always does so about 30 seconds into the run. Given that the successful runtime is about 2 min 30 s, and the run taking pretty exactly 2 mins, I'd suspect that it happens in one of the first iterations.
Expected behavior
The test should pass consistently.
To Reproduce
Steps to reproduce the behavior: submit a CI job several times (e.g. create any new branch, or commit to an existing one), eventually one of them will fail at tpv5-poro.
SeisSol/gitlab-cpu-pipeline.yml
Lines 36 to 78 in 4f89e56
poroelastic
material andRelease
configuration, precision does not matter. See here,SeisSol/gitlab-cpu-pipeline.yml
Lines 115 to 153 in 4f89e56
5-poro
.Screenshots/Console output
Cf. e.g. https://gitlab.lrz.de/ci_seissol/SeisSol/-/jobs/6781361
Especially line 241 there (https://gitlab.lrz.de/ci_seissol/SeisSol/-/jobs/6781361#L241 )
Additional context
None.
The text was updated successfully, but these errors were encountered: