a process.  The number of slots available are defined by the
environment in which PRRTE 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, PRRTE defaults to the number of processor cores
In all the above cases, if you want PRRTE 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 --map-by :OVERSUBSCRIBE option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
      Start 19: dbcsr_tensor_test
19/19 Test #19: dbcsr_tensor_test .....................................***Failed    0.11 sec
--------------------------------------------------------------------------
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:
  ./dbcsr_tensor_test
Either request fewer procs for your application, or make more slots
available for use.
A "slot" is the PRRTE term for an allocatable unit where we can
launch a process.  The number of slots available are defined by the
environment in which PRRTE 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, PRRTE defaults to the number of processor cores
In all the above cases, if you want PRRTE 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 --map-by :OVERSUBSCRIBE option to ignore the
number of available slots when deciding the number of processes to
launch.
--------------------------------------------------------------------------
0% tests passed, 19 tests failed out of 19
Total Test time (real) =   2.16 sec
The following tests FAILED:
	  1 - dbcsr_perf:inputs/test_H2O.perf (Failed)
	  2 - dbcsr_perf:inputs/test_rect1_dense.perf (Failed)
	  3 - dbcsr_perf:inputs/test_rect1_sparse.perf (Failed)
	  4 - dbcsr_perf:inputs/test_rect2_dense.perf (Failed)
	  5 - dbcsr_perf:inputs/test_rect2_sparse.perf (Failed)
	  6 - dbcsr_perf:inputs/test_singleblock.perf (Failed)
	  7 - dbcsr_perf:inputs/test_square_dense.perf (Failed)
	  8 - dbcsr_perf:inputs/test_square_sparse.perf (Failed)
	  9 - dbcsr_perf:inputs/test_square_sparse_bigblocks.perf (Failed)
	 10 - dbcsr_perf:inputs/test_square_sparse_rma.perf (Failed)
	 11 - dbcsr_unittest1 (Failed)
	 12 - dbcsr_unittest2 (Failed)
	 13 - dbcsr_unittest3 (Failed)
	 14 - dbcsr_unittest4 (Failed)
	 15 - dbcsr_tensor_unittest (Failed)
	 16 - dbcsr_tas_unittest (Failed)
	 17 - dbcsr_test_csr_conversions (Failed)
	 18 - dbcsr_test (Failed)
	 19 - dbcsr_tensor_test (Failed)
Errors while running CTest
+ test
error: Bad exit status from /var/tmp/rpm-tmp.S1yuYp (%check)
    Bad exit status from /var/tmp/rpm-tmp.S1yuYp (%check)
RPM build errors:
Child return code was: 1
EXCEPTION: [Error()]
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.9/site-packages/mockbuild/util.py", line 600, in do_with_status
    raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode)
mockbuild.exception.Error: Command failed: 
 # bash --login -c /usr/bin/rpmbuild -bb --target riscv64 --nodeps /builddir/build/SPECS/dbcsr.spec