Source: adios4dolfinx
Followup-For: Bug #1071722
Control: severity 1071722 important
This bug appears to arise from how openmpi needs to be invoked on a
specific system. It doesn't affect all systems, and doesn't affect
debian buildds or debci, so downgrading severity.
On 2024-05-26 12:44, Santiago Vila wrote:
To track that, what does `lscpu` report on your failing system?
(the thread,core,socket lines are probably the relevant ones)
It's an AWS machine of type m6a.large. These are the most relevant
specs.
Thread(s) per core: 2
Core(s) per
In such bug I proposed to run mpi with true and skip
the tests if it fails.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057556#34
Maybe a similar idea would work here as well.
We can try that. As you suggested in the other bug, it might be quirk of
openmpi we're facing.
openmpi
On 2024-05-25 18:31, Santiago Vila wrote:
El 25/5/24 a las 16:42, Drew Parsons escribió:
adios4dolfinx is building cleanly in reproducibility builds.
Perhaps the problem was a temporary glitch on your test system?
No, this is unlikely to be a temporary glitch:
...
My system has 2 CPUs,
El 25/5/24 a las 16:42, Drew Parsons escribió:
Source: adios4dolfinx
Followup-For: Bug #1071722
Control: tags -1 ftbfs
adios4dolfinx is building cleanly in reproducibility builds.
Perhaps the problem was a temporary glitch on your test system?
No, this is unlikely to be a temporary glitch:
Source: adios4dolfinx
Followup-For: Bug #1071722
Control: tags -1 ftbfs
adios4dolfinx is building cleanly in reproducibility builds.
Perhaps the problem was a temporary glitch on your test system?
Package: src:adios4dolfinx
Version: 0.8.1.post0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
7 matches
Mail list logo
