1-test-suite.log

1-test-suite.log (text/plain), 2.75 KB, created by Agostino Sarubbo on 2022-03-13 08:48:03 UTC

==========================================================
   PnetCDF 1.12.2: src/utils/ncvalidator/test-suite.log
==========================================================

# TOTAL: 2
# PASS:  0
# SKIP:  0
# XFAIL: 1
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

XFAIL: xfail_runs.sh
====================

XFAIL xfail_runs.sh (exit status: 1)

FAIL: wrap_runs.sh
==================

--------------------------------------------------------------------------
No network interfaces were found for out-of-band communications. We require
at least one available network for out-of-band messaging.
--------------------------------------------------------------------------
[localhost:00658] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file /var/tmp/portage/sys-cluster/openmpi-4.1.2/work/openmpi-4.1.2/orte/mca/ess/singleton/ess_singleton_module.c at line 716
[localhost:00658] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file /var/tmp/portage/sys-cluster/openmpi-4.1.2/work/openmpi-4.1.2/orte/mca/ess/singleton/ess_singleton_module.c at line 172
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  orte_ess_init failed
  --> Returned value Unable to start a daemon on the local node (-127) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Unable to start a daemon on the local node" (-127) instead of "Success" (0)
--------------------------------------------------------------------------
*** An error occurred in MPI_Init
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[localhost:00658] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed!
FAIL wrap_runs.sh (exit status: 1)