Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
  debian/rules build
dh build --max-parallel=1 --builddir=build
    dh_update_autotools_config -O--max-parallel=1 -O--builddir=build
    dh_autoreconf -O--max-parallel=1 -O--builddir=build
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:298: warning: The macro `AC_PROG_CC_C99' is obsolete.
configure.ac:298: You should run autoupdate.

[... snipped ...]

FAIL: validate_real_double_explicit_invert_triangular_default.sh
================================================================
--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

   ./validate_real_double_explicit_invert_triangular

Either request fewer slots for your application, or make more slots
available for use.

A "slot" is the Open MPI term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which Open MPI processes are run:

   1. Hostfile, via "slots=N" clauses (N defaults to number of
      processor cores if not provided)
   2. The --host command line parameter, via a ":N" suffix on the
      hostname (N defaults to 1 if not provided)
   3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
   4. If none of a hostfile, the --host command line parameter, or an
      RM is present, Open MPI defaults to the number of processor cores

In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.

Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
FAIL validate_real_double_explicit_invert_triangular_default.sh (exit status: 1)

FAIL: validate_real_double_invert_triangular_default.sh
=======================================================

--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

   ./validate_real_double_invert_triangular

Either request fewer slots for your application, or make more slots
available for use.

A "slot" is the Open MPI term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which Open MPI processes are run:

   1. Hostfile, via "slots=N" clauses (N defaults to number of
      processor cores if not provided)
   2. The --host command line parameter, via a ":N" suffix on the
      hostname (N defaults to 1 if not provided)
   3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
   4. If none of a hostfile, the --host command line parameter, or an
      RM is present, Open MPI defaults to the number of processor cores

In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.

Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
FAIL validate_real_double_invert_triangular_default.sh (exit status: 1)

SKIP: validate_multiple_objs_real_double_extended.sh
====================================================

SKIP validate_multiple_objs_real_double_extended.sh (exit status: 77)

SKIP: validate_multiple_objs_real_double_c_version_extended.sh
==============================================================

SKIP validate_multiple_objs_real_double_c_version_extended.sh (exit status: 77)

SKIP: validate_multiple_objs_real_double_cpp_version_extended.sh
================================================================

SKIP validate_multiple_objs_real_double_cpp_version_extended.sh (exit status: 77)

SKIP: validate_skewsymmetric_real_double_extended.sh
====================================================

SKIP validate_skewsymmetric_real_double_extended.sh (exit status: 77)

SKIP: validate_real_skewsymmetric_double_c_version_extended.sh
==============================================================

SKIP validate_real_skewsymmetric_double_c_version_extended.sh (exit status: 77)

SKIP: validate_real_skewsymmetric_double_cpp_version_extended.sh
================================================================

SKIP validate_real_skewsymmetric_double_cpp_version_extended.sh (exit status: 77)

SKIP: validate_split_comm_real_double_extended.sh
=================================================

SKIP validate_split_comm_real_double_extended.sh (exit status: 77)

FAIL: validate_double_instance_default.sh
=========================================

--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

   ./validate_double_instance

Either request fewer slots for your application, or make more slots
available for use.

A "slot" is the Open MPI term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which Open MPI processes are run:

   1. Hostfile, via "slots=N" clauses (N defaults to number of
      processor cores if not provided)
   2. The --host command line parameter, via a ":N" suffix on the
      hostname (N defaults to 1 if not provided)
   3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
   4. If none of a hostfile, the --host command line parameter, or an
      RM is present, Open MPI defaults to the number of processor cores

In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.

Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
FAIL validate_double_instance_default.sh (exit status: 1)

FAIL: validate_real_2stage_banded_default.sh
============================================

--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

   ./validate_real_2stage_banded

Either request fewer slots for your application, or make more slots
available for use.

A "slot" is the Open MPI term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which Open MPI processes are run:

   1. Hostfile, via "slots=N" clauses (N defaults to number of
      processor cores if not provided)
   2. The --host command line parameter, via a ":N" suffix on the
      hostname (N defaults to 1 if not provided)
   3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
   4. If none of a hostfile, the --host command line parameter, or an
      RM is present, Open MPI defaults to the number of processor cores

In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.

Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
FAIL validate_real_2stage_banded_default.sh (exit status: 1)

FAIL: validate_complex_2stage_banded_default.sh
===============================================

--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

   ./validate_complex_2stage_banded

Either request fewer slots for your application, or make more slots
available for use.

A "slot" is the Open MPI term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which Open MPI processes are run:

   1. Hostfile, via "slots=N" clauses (N defaults to number of
      processor cores if not provided)
   2. The --host command line parameter, via a ":N" suffix on the
      hostname (N defaults to 1 if not provided)
   3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
   4. If none of a hostfile, the --host command line parameter, or an
      RM is present, Open MPI defaults to the number of processor cores

In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.

Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
FAIL validate_complex_2stage_banded_default.sh (exit status: 1)

build/elpa2_print_kernels
  This program will give information on the ELPA2 kernels,
  which are available with this library and it will give
  information if (and how) the kernels can be choosen at
  runtime

   ELPA supports threads: no

  Information on ELPA2 real case:
  ===============================
   choice via environment variable: yes
   environment variable name      : ELPA_DEFAULT_real_kernel

   Available real kernels are:

    ELPA_2STAGE_REAL_GENERIC
    ELPA_2STAGE_REAL_GENERIC_SIMPLE
    ELPA_2STAGE_REAL_GENERIC_SIMPLE_BLOCK4
    ELPA_2STAGE_REAL_GENERIC_SIMPLE_BLOCK6


  Information on ELPA2 complex case:
  ===============================
   choice via environment variable: yes
   environment variable name      : ELPA_DEFAULT_complex_kernel

   Available complex kernels are:

    ELPA_2STAGE_COMPLEX_GENERIC
    ELPA_2STAGE_COMPLEX_GENERIC_SIMPLE


# error out in case of test suite failures
if grep ^FAIL build/test-suite.log; then exit 1; fi
FAIL: validate_c_version_complex_double_eigenvalues_1stage_analytic_explicit_default.sh
FAIL validate_c_version_complex_double_eigenvalues_1stage_analytic_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_c_version_complex_double_eigenvalues_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL validate_c_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvalues_1stage_analytic_explicit_default.sh
FAIL validate_c_version_real_double_eigenvalues_1stage_analytic_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_c_version_real_double_eigenvalues_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL validate_c_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_c_version_complex_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_cholesky_1stage_random_default.sh
FAIL validate_c_version_complex_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_c_version_real_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_cholesky_1stage_random_default.sh
FAIL validate_c_version_real_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_c_version_complex_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvectors_1stage_random_default.sh
FAIL validate_c_version_complex_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_c_version_real_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvectors_1stage_random_default.sh
FAIL validate_c_version_real_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_generalized_1stage_random_default.sh
FAIL validate_c_version_complex_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_generalized_1stage_random_default.sh
FAIL validate_c_version_real_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_generalized_decomp_1stage_random_default.sh
FAIL validate_c_version_complex_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_generalized_decomp_1stage_random_default.sh
FAIL validate_c_version_real_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_c_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_c_version_complex_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_c_version_real_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_c_version_real_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_solve_tridiagonal_1stage_toeplitz_default.sh
FAIL validate_c_version_real_double_solve_tridiagonal_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_cpp_version_complex_double_eigenvalues_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL validate_cpp_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_cpp_version_real_double_eigenvalues_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL validate_cpp_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_cpp_version_complex_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_cholesky_1stage_random_default.sh
FAIL validate_cpp_version_complex_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_cpp_version_real_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_cholesky_1stage_random_default.sh
FAIL validate_cpp_version_real_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_cpp_version_complex_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvectors_1stage_random_default.sh
FAIL validate_cpp_version_complex_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_cpp_version_real_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvectors_1stage_random_default.sh
FAIL validate_cpp_version_real_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_generalized_1stage_random_default.sh
FAIL validate_cpp_version_complex_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_generalized_1stage_random_default.sh
FAIL validate_cpp_version_real_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_generalized_decomp_1stage_random_default.sh
FAIL validate_cpp_version_complex_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_generalized_decomp_1stage_random_default.sh
FAIL validate_cpp_version_real_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_cpp_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_cpp_version_complex_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_cpp_version_real_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_cpp_version_real_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_solve_tridiagonal_1stage_toeplitz_default.sh
FAIL validate_cpp_version_real_double_solve_tridiagonal_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_1stage_analytic_default.sh
FAIL validate_complex_double_eigenvectors_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_2stage_default_kernel_analytic_default.sh
FAIL validate_complex_double_eigenvectors_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_analytic_default.sh
FAIL validate_real_double_eigenvectors_1stage_analytic_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_analytic_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_analytic_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvalues_1stage_frank_default.sh
FAIL validate_real_double_eigenvalues_1stage_frank_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvalues_2stage_default_kernel_frank_default.sh
FAIL validate_real_double_eigenvalues_2stage_default_kernel_frank_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_frank_default.sh
FAIL validate_real_double_eigenvectors_1stage_frank_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_frank_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_frank_default.sh (exit status: 1)
FAIL: validate_real_double_hermitian_multiply_1stage_frank_default.sh
FAIL validate_real_double_hermitian_multiply_1stage_frank_default.sh (exit status: 1)
FAIL: validate_complex_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_complex_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_complex_double_cholesky_1stage_random_default.sh
FAIL validate_complex_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_real_double_cholesky_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_cholesky_1stage_random_default.sh
FAIL validate_real_double_cholesky_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_cholesky_1stage_random_split_comm_myself_explicit_default.sh
FAIL validate_real_double_cholesky_1stage_random_split_comm_myself_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_cholesky_1stage_random_split_comm_myself_default.sh
FAIL validate_real_double_cholesky_1stage_random_split_comm_myself_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_complex_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_1stage_random_default.sh
FAIL validate_complex_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_complex_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_random_explicit_default.sh
FAIL validate_real_double_eigenvectors_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_random_default.sh
FAIL validate_real_double_eigenvectors_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_random_split_comm_myself_explicit_default.sh
FAIL validate_real_double_eigenvectors_1stage_random_split_comm_myself_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_random_split_comm_myself_default.sh
FAIL validate_real_double_eigenvectors_1stage_random_split_comm_myself_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_random_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_random_split_comm_myself_explicit_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_random_split_comm_myself_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_random_split_comm_myself_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_random_split_comm_myself_default.sh (exit status: 1)
FAIL: validate_complex_double_generalized_1stage_random_all_layouts_default.sh
FAIL validate_complex_double_generalized_1stage_random_all_layouts_default.sh (exit status: 1)
FAIL: validate_complex_double_generalized_1stage_random_default.sh
FAIL validate_complex_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_generalized_1stage_random_all_layouts_default.sh
FAIL validate_real_double_generalized_1stage_random_all_layouts_default.sh (exit status: 1)
FAIL: validate_real_double_generalized_1stage_random_default.sh
FAIL validate_real_double_generalized_1stage_random_default.sh (exit status: 1)
FAIL: validate_complex_double_generalized_decomp_1stage_random_default.sh
FAIL validate_complex_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_generalized_decomp_1stage_random_default.sh
FAIL validate_real_double_generalized_decomp_1stage_random_default.sh (exit status: 1)
FAIL: validate_complex_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_complex_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_complex_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_complex_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_real_double_hermitian_multiply_1stage_random_explicit_default.sh
FAIL validate_real_double_hermitian_multiply_1stage_random_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_hermitian_multiply_1stage_random_default.sh
FAIL validate_real_double_hermitian_multiply_1stage_random_default.sh (exit status: 1)
FAIL: validate_complex_double_cholesky_1stage_toeplitz_default.sh
FAIL validate_complex_double_cholesky_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_cholesky_1stage_toeplitz_default.sh
FAIL validate_real_double_cholesky_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvalues_1stage_toeplitz_explicit_default.sh
FAIL validate_complex_double_eigenvalues_1stage_toeplitz_explicit_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvalues_1stage_toeplitz_default.sh
FAIL validate_complex_double_eigenvalues_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvalues_2stage_default_kernel_toeplitz_default.sh
FAIL validate_complex_double_eigenvalues_2stage_default_kernel_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvalues_1stage_toeplitz_explicit_default.sh
FAIL validate_real_double_eigenvalues_1stage_toeplitz_explicit_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvalues_1stage_toeplitz_default.sh
FAIL validate_real_double_eigenvalues_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvalues_2stage_default_kernel_toeplitz_default.sh
FAIL validate_real_double_eigenvalues_2stage_default_kernel_toeplitz_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_1stage_toeplitz_default.sh
FAIL validate_complex_double_eigenvectors_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_complex_double_eigenvectors_2stage_default_kernel_toeplitz_default.sh
FAIL validate_complex_double_eigenvectors_2stage_default_kernel_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_1stage_toeplitz_default.sh
FAIL validate_real_double_eigenvectors_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_eigenvectors_2stage_default_kernel_toeplitz_default.sh
FAIL validate_real_double_eigenvectors_2stage_default_kernel_toeplitz_default.sh (exit status: 1)
FAIL: validate_real_double_solve_tridiagonal_1stage_toeplitz_default.sh
FAIL validate_real_double_solve_tridiagonal_1stage_toeplitz_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_explicit_invert_triangular_default.sh
FAIL validate_c_version_complex_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_c_version_complex_double_invert_triangular_default.sh
FAIL validate_c_version_complex_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_explicit_invert_triangular_default.sh
FAIL validate_c_version_real_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_c_version_real_double_invert_triangular_default.sh
FAIL validate_c_version_real_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_explicit_invert_triangular_default.sh
FAIL validate_cpp_version_complex_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_cpp_version_complex_double_invert_triangular_default.sh
FAIL validate_cpp_version_complex_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_explicit_invert_triangular_default.sh
FAIL validate_cpp_version_real_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_cpp_version_real_double_invert_triangular_default.sh
FAIL validate_cpp_version_real_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_complex_double_explicit_invert_triangular_default.sh
FAIL validate_complex_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_complex_double_invert_triangular_default.sh
FAIL validate_complex_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_real_double_explicit_invert_triangular_default.sh
FAIL validate_real_double_explicit_invert_triangular_default.sh (exit status: 1)
FAIL: validate_real_double_invert_triangular_default.sh
FAIL validate_real_double_invert_triangular_default.sh (exit status: 1)
FAIL: validate_double_instance_default.sh
FAIL validate_double_instance_default.sh (exit status: 1)
FAIL: validate_real_2stage_banded_default.sh
FAIL validate_real_2stage_banded_default.sh (exit status: 1)
FAIL: validate_complex_2stage_banded_default.sh
FAIL validate_complex_2stage_banded_default.sh (exit status: 1)
make[1]: *** [debian/rules:47: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:36: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

severity 1057556 normal
retitle 1057556 elpa: FTBFS unless machine has more than one vcore
thanks

Hi Santiago,

[...]

So you are building elpa on a machine/vm with one cpu/vcore apparently?

I guess it is useful information that elpa requires at least two cores
to executes its MPI-based testsuite, but I don't think that this should
be a general requirement for an RC bug, so downgrading to normal for
now. If you indeed have more than 1 cpu core/vcore available, then I
agree that this is RC.


Michael

El 11/12/23 a las 14:08, Michael Banck escribió:

No. In this case the build was made on an AWS machine of type m6a.large,
which has 2 vcores. I'm usually including the machine type in the hostname,
so that it may be found in the very first line of the full build log:

sbuild (Debian sbuild) 0.85.0 (04 January 2023) on m6a-large-1701732603

The specs for m6a.large machines are available here:

https://aws.amazon.com/ec2/instance-types/m6a/

I think the end user should never have to deal with such "useful information".

If it is possible to detect beforehand that the test suite will fail on a given
system, then the package should probably enclose dh_auto_test inside a
suitable Makefile if/endif block.

Alternatively, if the number "2" at the end of the debian/rules
line saying "export TEST_FLAGS=200 12 2" is the number of vcores
requested for the tests, then the package should probably honor
DEB_BUILD_OPTIONS=parallel=n so that no more vcores than available
are requested.

Thanks.

El 11/12/23 a las 14:50, Santiago Vila escribió:

Hmm. Actually, the problem may be more subtle than that.

If the number 2 in TEST_FLAGS is really the number of cores
and the machine is detected as having "one core, two threads",
then requesting 2 cores (four threads) will not work.

Could this be a problem with openmpi, which miscounts
cores/vcpus?

Thanks.

Hi,

Hrm, ok.

Note that the end user is not seeing this problem, they are installing
the binary packages and are not, in general, running the test suite.

Good point, I will investigate this.


Thanks,

Michael

tags 1057556 + patch
thanks

Hello.

This is my proposal to fix this bug, but it needs some review.

(Side note: I see "Running tests with matrix size" in the build log,
so not sure if the ${TEST_FLAGS% *} thing is correct).

In summary: We run "mpiexec -n 2 true" first as a test
to ensure that the machine has enough slots. If this does
not even work, we assume that the user just want to rebuild
the package from source on a system which can't run the test
suite at all. The package appears as "reproducible" in the
reproducible builds framework, so the risk of doing this
is quite low.

I've split my changes in three different commits, with
an explanation for each of them.

As you will see, I am really willing to help...

... so please honor your word and restore the original severity.

Thanks.

Hello.

Instead of patch-2.txt and patch-3.txt, the following more simple patch
would also fix the issue (I've tested it on single-cpu systems and also
on m6a.large instances from AWS, which have 1 core and two threads).

(Suggested by Drew Parsons in Bug#1071722, which is similar to this one).

(IMO the patch called patch-1.txt which I posted before should still be
applied because it removes unnecessary complexity).

Thanks.

On Fri, 31 May 2024 14:46:28 +0200 Santiago Vila <sanvila@debian.org>
wrote:> Instead of patch-2.txt and patch-3.txt, the following more
simple patch

This an un-intrusive patch allowing elpa to be built even on
single-vcore machines. I will apply it.

Indeed.

Thanks for caring for elpa.

Andrius

Hello,

Bug #1057556 in elpa reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debichem-team/elpa/-/commit/2724edc4ca09a75b0c9822fcd9da9a8bb25de633

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057556

We believe that the bug you reported is fixed in the latest version of
elpa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057556@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrius Merkys <merkys@debian.org> (supplier of updated elpa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 07 Jun 2024 11:52:08 -0400
Source: elpa
Architecture: source
Version: 2022.11.001-3
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team <debichem-devel@lists.alioth.debian.org>
Changed-By: Andrius Merkys <merkys@debian.org>
Closes: 1057556
Changes:
 elpa (2022.11.001-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop ifeq for nocheck, debhelper already does automatically.
     Thanks Santiago Vila.
   * Fix building on single-vcore machines (Closes: #1057556).
     Thanks Santiago Vila.
Checksums-Sha1:
 a3bded5fa15a1565965032a8b7d2d1c7eab29cac 2120 elpa_2022.11.001-3.dsc
 22789a52e833a8a49c26ad83f25f49163cfd671b 17664 elpa_2022.11.001-3.debian.tar.xz
 c7a72d39ebc470bd97c984b3d86ad78415441db7 8956 elpa_2022.11.001-3_source.buildinfo
Checksums-Sha256:
 aab496e6ddd0b259b30efc373e7551e02f3a91a91bd5de6d251824e6d7d15587 2120 elpa_2022.11.001-3.dsc
 91e1d4bbff5380c1aa3a77717db45ff6674a35059259e9fdf6555c9290407ea9 17664 elpa_2022.11.001-3.debian.tar.xz
 384826ed7730ff95f73900af65ca1acc3c6ca69c8d7445ef13097c27ed847cf8 8956 elpa_2022.11.001-3_source.buildinfo
Files:
 65f53fcb47a72322672d1fb3a08e0628 2120 science optional elpa_2022.11.001-3.dsc
 11a1d05bf2ce2cce505137938f9ba32e 17664 science optional elpa_2022.11.001-3.debian.tar.xz
 188caaeb34aa80654ecf2f4476388595 8956 science optional elpa_2022.11.001-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmZl8/0SHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKH2xQQAIttmYVEa/6pQKpmkckNyRW8x6WSfp86
OrYlXN82n8y+VJ0UHvB6HWp7/6SzwU3WP7JN64Lcp+xrD2dy57nWNFEJPq5V0IaQ
EklHsvqPzWVC+PwKmnrtdguxXxuoI09BBQsHOnDlYrnQQVPrYhoFYXpDVpLA1wqK
JJ9rmtIi15H35NMqO7BV5Jh5eaPOyR7w21qqHbQffv1tYioT3RPVPYC0jbQYovBT
RGReZX2mKY9zNkUOtP4FCfVFoKG8Ms0Scapzap0EbyDwEZmWAjVEjgf+OXVOJ8Kl
5BTItMJnXIqSM91RrRNlMyit1y1/husuqHXdzzNpQOUC6MfEen2e72M0a9xykJvW
N+zOoDfl6A7sZEKch6xxu7PLmyhlTyxIRWcbq6ry3NpG70aMkp8lg15cc4G1wQpd
ZMDpfC0J4bjgAlR5ok1mVylQjgv0E4B/3QYDpMCRv4cVwJmDWUBZ2Ck0K29pGV2D
qf+ek69AT3bgdVEfDuqPwmetTmpnaeV3loDR2k2Iy9sDi5lK6LEId57EjcrEd2qo
a0HY9Enydzkg9Hxhe0hOp+n4ERrgrJ7HZoOB8mr4w3ElvECwCIuorT0iwZDHQPOq
o1PWriWP9E2XnOGBuHYqt/Gm0IuA63QjzWm34Pk1rs7Bw9vQUMO3yFNPPYx+v0Mz
xaBrqq6AnA8t
=G3OO
-----END PGP SIGNATURE-----

We believe that the bug you reported is fixed in the latest version of
elpa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057556@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila <sanvila@debian.org> (supplier of updated elpa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 31 Dec 2024 13:25:00 +0100
Source: elpa
Architecture: source
Version: 2022.11.001-2+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debichem Team <debichem-devel@lists.alioth.debian.org>
Changed-By: Santiago Vila <sanvila@debian.org>
Closes: 1057556
Changes:
 elpa (2022.11.001-2+deb12u1) bookworm; urgency=medium
 .
   * Team upload.
   * Enable oversubscribe to run the tests, allowing the package
     to be built when less than 2 slots are detected. This not only
     happens on machines with 1 CPU but also on some AWS machines
     with 2 vCPUs like c6a.large or m6a.large. Closes: #1057556.
Checksums-Sha1:
 f0da1009bf4cbdce39499c2ef5a0b87f1be91f64 1782 elpa_2022.11.001-2+deb12u1.dsc
 80fb8b49c04bab5e90a1c83f352ab1355eaaa7e2 17744 elpa_2022.11.001-2+deb12u1.debian.tar.xz
 a168aba92aa2e52b23b22eabfeebec2c9a836611 7439 elpa_2022.11.001-2+deb12u1_source.buildinfo
Checksums-Sha256:
 c5c63ebe1c4469537f5bdb548d74768c680151cff8d4ba4bdeda4d0c38c1a25b 1782 elpa_2022.11.001-2+deb12u1.dsc
 5cb90c32660b6086afdc6b3cd87311e65101ba1c2f7d7cc7113c19eaca62ed67 17744 elpa_2022.11.001-2+deb12u1.debian.tar.xz
 ebe65d46d635cf6375655461d71410a33caa68a17973e1dfc501a1b64dc041cd 7439 elpa_2022.11.001-2+deb12u1_source.buildinfo
Files:
 c65d049ac5315c8985fd0c4fc61145d8 1782 science optional elpa_2022.11.001-2+deb12u1.dsc
 a0195430ed1914ec87edaf9545cf5cdf 17744 science optional elpa_2022.11.001-2+deb12u1.debian.tar.xz
 b619b69bc6427cce7828e2db37e7bd8c 7439 science optional elpa_2022.11.001-2+deb12u1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmeCdpwACgkQQc5/C58b
izKyUAf+LhNwUz9975luTEj3lMY29cALCyx0NLl14LBLFRWwpLhOv4lJ9jnzKeJP
GJzQpTMlrctP1okB6GgBGbMv1LCyzzg0vkLTEp3/XQhgyAXlrJ7xD+iE7q9eH1ax
33/FL/JZZ8/SQcWe55ypl1jimSj7JcxZjiX8kjYNeGd+RB4d1h6E9dFX7XSwrJjG
e7D9Ztdxte6iCp3rq4Gux4QHHrM/6EiPn7ayksTzbf7uqdZScqmhfdrFGHejzLzd
S8wzCQWOWu9QKAZrPldoy6VROU4X5rqwSgYXctF0jsHXxeDq9QK0sgFqJ8i5WpwE
Jj3guuSNgowqAjirMXmavaMlTDy1+A==
=JhUj
-----END PGP SIGNATURE-----

notfixed 1057556 2022.11.001-3
thanks

Hi. I'm marking this as notfixed in unstable because the current
fix was for OpenMPI 4 and does not work anymore with OpenMPI 5.

Several months ago Graham asked me not to touch the package
because he was going to work on it, so I did not touch it.

I know that this is fixed in experimental, but I'd like to
see it fixed in trixie so that I don't have to make another
stable-proposed-updates upload as I already did in bookworm.

Can someone advise about what to do?

If it's a matter of uploading the current version in experimental
to unstable, I'd prefer Graham to do it, since he is the one who
authored the experimental versions.

On the other hand, if this is not expected to happen, then I'd like
to have your permission to fix this based on the current version
(say, in a branch called trixie and versioned 2022.11.001-4), that
can be merged back to master at a later time.

Thanks.

Hi Santiago and Michael

No, that was Michael.  I did look at uploading 2024.05.001-2 to
unstable.  It doesn't appear to start a library transition, and gpaw
continues to work with the new version.  I was concerned about the
apparent breakage caused in cp2k, with which I am not familiar.  This
showed up in the pseudo-excuses for elpa in experimental [1].

I'd prefer MIchael to go ahead with 2024.05.001-2 to unstable, but I'm
also happy to upload 2022.11.001-4 which I was working on previously.

Regards
Graham


[1] https://qa.debian.org/excuses.php?package=elpa&experimental=1

Hi Michael

I'll assume you are not working on uploading 2024.05.001-2 to unstable.

I should have time this weekend (April 26 - 27) to work on an upload
of  2022.11.001-4.

Regards
Graham

Hi Graham,

Yeah sorry, I felt like time was running out for trixie on this one.

I might have some time next week, but I am awfully busy with the job and
private life right now :-/

That'd be appreciated.


Michael