El 30/5/25 a las 22:35, Drew Parsons escribió:
Source: pymatgen
Followup-For: Bug #1106436
pymatgen tests are known to be broadly flakey.
If you run your build test again, it will likely pass.
That's not how it works.
By the time I get to the point of reporting a FTBFS bugs,
I've already tried several times and it failed several times
in a row on several different machines.
This is my build history before I reported this one:
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T114313.018Z
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T121603.326Z
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T121604.134Z
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T121607.914Z
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T121608.444Z
Status: failed pymatgen_2025.2.18+dfsg1-4_amd64-20250524T121609.251Z
Now, if you tell me that this is due to some build-dependency which
has changed since 20250524, yes, I could try again, but if no build-dependency
has changed, there are no reasons to expect a different result.
Thanks.
