Source: dolfin
Followup-For: Bug #920546
dolfin tests have been reliably passing now since 2019.1.0 was
uploaded.
I think we can consider this bug resolved now, whether by dolfin
2019.1 itself or by the openmpi (or petsc) upgrades that happened in
the same time frame.
Source: dolfin
Followup-For: Bug #920546
Took a while, but we eventually got the timeout error again in a debci
test for 2019.1.0. One fail after 32 successful tests. That's
evidently much less frequent than the timeout errors for 2018.1.0,
indicating the new version has fixed some of the race
Source: dolfin
Followup-For: Bug #920546
I have a hunch the timeout problem might be related to
oversubscription of CPUs in mpi runs.
(in principle the same would apply to python MPI tests, presumeably
the python/MPI interface would "slow down" messages enough to avoid
the race condition)
I've
Source: dolfin
Followup-For: Bug #920546
The flaky test has been nasty the last couple of days. Always the C++
MPI demos timing out, each time on a different demo. The MPI python
demos (usually) run fine. Presumeably some unresolved race condition.
2019.1 is now released (currently in
Source: dolfin
Followup-For: Bug #920546
It is a bit of a nuisance. The timeout doesn't happen every time, and
when it does happen, it's hanging on a different MPI test each time.
So not so simple to fix, apart from shutting down all MPI tests but
that seems a step too far. Fortunately the
Source: dolfin
Version: 2018.1.0.post1-13
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout
Dear maintainers,
Since you uploaded your package version 2018.1.0.post1-13, it has failed
several times on your test-dolfin-cpp test on
6 matches
Mail list logo
