On Sun, Aug 23, 2026 at 05:01:44PM +0200, Michael Banck wrote:
> On Thu, Aug 06, 2026 at 10:30:17AM +0000, Santiago Vila wrote:
> > During a rebuild of all packages in unstable, this package failed to
> > build.
>
> I don't see that when I try to rebuild cp2k, I think it was a transient
> issue, can you try again?
You are right that the precise error which I reported does no longer happen.
I was indeed able to rebuild the package without errors on 2026-08-10
but yesterday it started to fail again, now in this way:
------------------------------------------------------------------
*******************************************************************************
* ___ *
* / \ *
* [ABORT] *
* \___/ MPI error 5 in mpi_comm_rank @ mp_comm_size : MPI_ERR_COMM: *
* | invalid communicator *
* O/| *
* /| | *
* / \ mpiwrap/message_passing.F:1305 *
*******************************************************************************
===== Routine Calling Stack =====
8 mp_comm_size
7 arnoldi_extremal
6 qs_ot_get_p
5 ot_scf_init
4 init_scf_loop
3 scf_env_do_scf
2 qs_energies
1 CP2K
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
Proc: [[23235,1],0]
Errorcode: 1
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
------------------------------------------------------------------
For reference, I've put my last failed build log (made yesterday)
in the same directory as before:
https://people.debian.org/~sanvila/build-logs/202608/
Can we retitle the bug, or do you prefer to close it
so that I report a brand new one?
(I've started yet another rebuild today to be sure).
Thanks.
