==> Synchronizing chroot copy [/home/alhp/workspace/chroot/root] -> [build_e4ea6541-4c1c-4cf8-a07d-d5d5bfc1d790]...done ==> Making package: paraview-catalyst 2.0.0-1.1 (Wed Nov 20 14:34:10 2024) ==> Retrieving sources... -> Downloading catalyst-v2.0.0.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 12 818k 12 103k 0 0 130k 0 0:00:06 --:--:-- 0:00:06 130k 100 818k 100 818k 0 0 738k 0 0:00:01 0:00:01 --:--:-- 739k ==> Validating source files with b2sums... catalyst-v2.0.0.tar.gz ... Passed ==> Making package: paraview-catalyst 2.0.0-1.1 (Wed Nov 20 14:34:14 2024) ==> Checking runtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... Package (11) New Version Net Change extra/hwloc 2.11.2-1 1.64 MiB extra/libfabric 1.22.0-2 4.12 MiB core/libnl 3.11.0-1 2.08 MiB extra/libpciaccess 0.18.1-2 0.06 MiB core/mpdecimal 4.0.0-2 0.32 MiB extra/numactl 2.0.19-1 0.24 MiB extra/openpmix 5.0.3-1 3.67 MiB extra/openucx 1.17.0-3 6.14 MiB extra/prrte 3.0.6-1 1.87 MiB extra/openmpi 5.0.5-2 9.92 MiB core/python 3.12.7-1 70.07 MiB Total Installed Size: 100.14 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing libpciaccess... installing hwloc... Optional dependencies for hwloc cairo: PDF, Postscript, and PNG export support libxml2: full XML import/export support [installed] installing numactl... installing libfabric... installing libnl... installing openpmix... Optional dependencies for openpmix openpmix-docs: for documentation installing openucx... Optional dependencies for openucx rdma-core: for InfiniBand and RDMA support cuda: for CUDA support rocm-language-runtime: for ROCm support installing prrte... Optional dependencies for prrte openssh: for execution on remote hosts via plm_ssh_agent prrte-docs: for documentation installing openmpi... Optional dependencies for openmpi cuda: cuda support hip-runtime-amd: ROCm support gcc-fortran: fortran support openssh: for execution on remote hosts via plm_ssh_agent openucc: for UCC accelerated collectives installing mpdecimal... installing python... Optional dependencies for python python-setuptools: for building Python packages using tooling that is usually bundled with Python python-pip: for installing Python packages using tooling that is usually bundled with Python python-pipx: for installing Python software not packaged on Arch Linux sqlite: for a default database integration [installed] xz: for lzma [installed] tk: for tkinter :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate... ==> Checking buildtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... Package (14) New Version Net Change extra/blas 3.12.0-5 0.65 MiB extra/cblas 3.12.0-5 0.34 MiB extra/cppdap 1.58.0-2 1.55 MiB extra/hicolor-icon-theme 0.18-1 0.05 MiB extra/jsoncpp 1.9.6-3 0.77 MiB extra/lapack 3.12.0-5 7.48 MiB extra/libuv 1.49.2-1 0.61 MiB extra/rhash 1.4.4-1 0.32 MiB extra/cmake 3.31.0-1 77.86 MiB core/gcc-fortran 14.2.1+r134+gab884fffe3fc-1 44.26 MiB extra/gtest 1.15.2-1 2.16 MiB extra/ninja 1.12.1-1 0.38 MiB extra/python-mpi4py 4.0.0-1 3.32 MiB extra/python-numpy 2.1.3-1 47.58 MiB Total Installed Size: 187.32 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing cppdap... installing hicolor-icon-theme... installing jsoncpp... Optional dependencies for jsoncpp jsoncpp-doc: documentation installing libuv... installing rhash... installing cmake... Optional dependencies for cmake make: for unix Makefile generator [installed] ninja: for ninja generator [pending] qt6-base: cmake-gui installing gcc-fortran... installing gtest... Optional dependencies for gtest python: gmock generator [installed] installing ninja... installing blas... installing cblas... installing lapack... installing python-numpy... Optional dependencies for python-numpy blas-openblas: faster linear algebra installing python-mpi4py... :: Running post-transaction hooks... (1/2) Arming ConditionNeedsUpdate... (2/2) Updating the info directory file... ==> Retrieving sources... -> Found catalyst-v2.0.0.tar.gz ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources... -> Extracting catalyst-v2.0.0.tar.gz with bsdtar ==> Starting prepare()... ==> Starting build()... -- The C compiler identification is GNU 14.2.1 -- The CXX compiler identification is GNU 14.2.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development NumPy Interpreter Development.Module Development.Embed -- The Fortran compiler identification is GNU 14.2.1 -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Check for working Fortran compiler: /usr/bin/gfortran - skipped -- Setting build type to 'Debug' as none was specified. -- Found MPI_C: /usr/lib/libmpi.so (found version "3.1") -- Found MPI: TRUE (found version "3.1") found components: C -- Looking for sys/types.h -- Looking for sys/types.h - found -- Looking for stdint.h -- Looking for stdint.h - found -- Looking for stddef.h -- Looking for stddef.h - found -- Check size of char -- Check size of char - done -- Check size of short -- Check size of short - done -- Check size of int -- Check size of int - done -- Check size of long -- Check size of long - done -- Check size of float -- Check size of float - done -- Check size of double -- Check size of double - done -- Check size of long long -- Check size of long long - done -- Check size of long float -- Check size of long float - failed -- Check size of long double -- Check size of long double - done -- Check size of void * -- Check size of void * - done -- Bitwidth Mapping: preferring `long` over `long long` for c++11 compatibility -- Bitwidth Mapping Results: -- conduit::int8 native type: signed char -- conduit::int16 native type: signed short -- conduit::int32 native type: signed int -- conduit::int64 native type: signed long -- conduit::uint8 native type: unsigned char -- conduit::uint16 native type: unsigned short -- conduit::uint32 native type: unsigned int -- conduit::uint64 native type: unsigned long -- conduit::float32 native type: float -- conduit::float64 native type: double -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success -- Found GTest: /usr/lib/cmake/GTest/GTestConfig.cmake (found version "1.15.2") -- Adding conduit lib unit tests -- Found Threads: TRUE -- Configuring done (1.6s) -- Generating done (0.0s) -- Build files have been written to: /startdir/src/build [1/130] Building Fortran preprocessed thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/fortran/conduit_fortran.F90-pp.f90 f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [2/130] Generating Fortran dyndep file thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/Fortran.dd [3/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_endianness.cpp.o [4/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/c/conduit_c.cpp.o [5/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/c/conduit_datatype_c.cpp.o [6/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_error.cpp.o [7/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/c/conduit_utils_c.cpp.o [8/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/c/conduit_cpp_to_c.cpp.o [9/130] Building Fortran object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/fortran/conduit_fortran.F90.o f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [10/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_log.cpp.o [11/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_core.cpp.o [12/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_data_type.cpp.o [13/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_node_iterator.cpp.o [14/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_data_accessor.cpp.o [15/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint.cpp.o [16/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_ndarray_index.cpp.o [17/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mcarray.cpp.o [18/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh_matset_xforms.cpp.o [19/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_schema.cpp.o [20/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_o2mrelation_utils.cpp.o [21/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/c/conduit_node_c.cpp.o [22/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_o2mrelation_index.cpp.o [23/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_o2mrelation.cpp.o [24/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_zfparray.cpp.o [25/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_generator.cpp.o [26/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/c/conduit_blueprint_c.cpp.o [27/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_o2mrelation_iterator.cpp.o [28/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_table.cpp.o [29/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/dumper.c.o [30/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/loader.c.o [31/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/c/conduit_blueprint_mcarray_c.cpp.o [32/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/reader.c.o [33/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/api.c.o [34/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/c/conduit_blueprint_table_c.cpp.o [35/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/writer.c.o [36/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/parser.c.o [37/130] Building CXX object thirdparty/conduit/libb64/CMakeFiles/catalyst_conduit_b64.dir/src/cdecode.cpp.o [38/130] Building CXX object thirdparty/conduit/libb64/CMakeFiles/catalyst_conduit_b64.dir/src/cencode.cpp.o [39/130] Building CXX object src/catalyst/CMakeFiles/catalyst.dir/catalyst_api_default.cpp.o [40/130] Building C object src/catalyst/CMakeFiles/catalyst.dir/catalyst_conduit_abi_internal.c.o [41/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/c/conduit_blueprint_mesh_c.cpp.o [42/130] Generating Fortran dyndep file src/catalyst/CMakeFiles/catalyst.dir/Fortran.dd [43/130] Building Fortran preprocessed src/wrap/fortran/CMakeFiles/catalyst_fortran.dir/catalyst_api.f90-pp.f90 f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [44/130] Building C object src/catalyst/CMakeFiles/catalyst.dir/catalyst_api.c.o [45/130] Generating Fortran dyndep file src/wrap/fortran/CMakeFiles/catalyst_fortran.dir/Fortran.dd [46/130] Building Fortran preprocessed tests/catalyst_tests/CMakeFiles/test_double_impl_f.dir/test_double_impl.f90-pp.f90 f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [47/130] Generating Fortran dyndep file tests/catalyst_tests/CMakeFiles/test_double_impl_f.dir/Fortran.dd [48/130] Building Fortran object src/wrap/fortran/CMakeFiles/catalyst_fortran.dir/catalyst_api.f90.o f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [49/130] Building CXX object src/catalyst/CMakeFiles/catalyst.dir/catalyst_stub.cpp.o [50/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/emitter.c.o [51/130] Building CXX object src/catalyst/CMakeFiles/catalyst.dir/catalyst_python_tools.cpp.o [52/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh_utils.cpp.o [53/130] Building CXX object thirdparty/conduit/conduit/python/CMakeFiles/conduit_utils_python.dir/conduit_utils_python.cpp.o [54/130] Building CXX object thirdparty/conduit/blueprint/python/CMakeFiles/conduit_blueprint_python.dir/conduit_blueprint_python.cpp.o [55/130] Building C object src/impl-stub/CMakeFiles/catalyst_stub.dir/catalyst_impl_stub.c.o [56/130] Building CXX object thirdparty/conduit/blueprint/python/CMakeFiles/conduit_blueprint_mcarray_python.dir/conduit_blueprint_mcarray_python.cpp.o [57/130] Building C object thirdparty/conduit/libyaml/CMakeFiles/catalyst_conduit_libyaml.dir/src/scanner.c.o [58/130] Building CXX object thirdparty/conduit/blueprint/python/CMakeFiles/conduit_blueprint_table_python.dir/conduit_blueprint_table_python.cpp.o [59/130] Building CXX object thirdparty/conduit/blueprint/python/CMakeFiles/conduit_blueprint_mesh_python.dir/conduit_blueprint_mesh_python.cpp.o [60/130] Building CXX object tests/abi_tests/CMakeFiles/test_catalyst_abi.dir/test_catalyst_abi.cpp.o [61/130] Building CXX object src/impl-stub/CMakeFiles/catalyst_stub.dir/catalyst.cxx.o [62/130] Building C object tests/catalyst_tests/CMakeFiles/test_double_impl.dir/test_double_impl.c.o [63/130] Building C object tests/catalyst_tests/CMakeFiles/test_catalyst_results.dir/catalyst_results/test_catalyst_results.c.o [64/130] Building C object tests/catalyst_tests/CMakeFiles/test_external_conduit_impl.dir/test_external_conduit_impl.c.o [65/130] Building C object tests/catalyst_tests/CMakeFiles/test_internal_conduit_impl.dir/test_internal_conduit_impl.c.o [66/130] Building Fortran object tests/catalyst_tests/CMakeFiles/test_double_impl_f.dir/test_double_impl.f90.o f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [67/130] Building CXX object tests/abi_tests/CMakeFiles/test_conduit_abi.dir/test_conduit_abi.cpp.o [68/130] Building C object tests/catalyst_tests/impls/CMakeFiles/catalyst-external-conduit.dir/catalyst_impl_external_conduit.c.o [69/130] Building C object tests/catalyst_tests/impls/CMakeFiles/catalyst-double.dir/catalyst_impl_double.c.o [70/130] Building CXX object tests/catalyst_tests/impls/CMakeFiles/catalyst-double.dir/double.cpp.o [71/130] Building CXX object src/wrap/python/CMakeFiles/catalyst_python.dir/catalyst_python.cpp.o [72/130] Building CXX object tests/catalyst_tests/impls/CMakeFiles/catalyst-external-conduit.dir/external-conduit.cpp.o [73/130] Building C object tests/catalyst_tests/impls/CMakeFiles/catalyst-internal-conduit.dir/catalyst_impl_internal_conduit.c.o [74/130] Building CXX object tests/catalyst_tests/impls/CMakeFiles/catalyst-internal-conduit.dir/internal-conduit.cpp.o [75/130] Building CXX object tests/catalyst_tests/CMakeFiles/test_catalyst_conduit.dir/catalyst_conduit/test_catalyst_conduit.cpp.o [76/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_info.dir/t_conduit_node_info.cpp.o [77/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_parent.dir/t_conduit_node_parent.cpp.o [78/130] Building CXX object thirdparty/conduit/conduit/python/CMakeFiles/conduit_python.dir/conduit_python.cpp.o [79/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_paths.dir/t_conduit_node_paths.cpp.o [80/130] Copying catalyst_conduit/__init__.py to the binary directory [81/130] Copying catalyst_conduit/blueprint/__init__.py to the binary directory [82/130] Copying catalyst_conduit/blueprint/mcarray/__init__.py to the binary directory [83/130] Copying catalyst_conduit/blueprint/mesh/__init__.py to the binary directory [84/130] Copying catalyst_conduit/blueprint/table/__init__.py to the binary directory [85/130] Copying catalyst_conduit/utils/__init__.py to the binary directory [86/130] Copying catalyst/__init__.py to the binary directory [87/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_to_string.dir/t_conduit_to_string.cpp.o [88/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_utils.cpp.o [89/130] Building CXX object src/tools/replay/CMakeFiles/catalyst_replay.dir/catalyst_replay.cpp.o [90/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_compare.dir/t_conduit_node_compare.cpp.o [91/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_data_array.cpp.o [92/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_to_value.dir/t_conduit_node_to_value.cpp.o [93/130] Building CXX object thirdparty/conduit/conduit/CMakeFiles/catalyst_conduit.dir/conduit_node.cpp.o [94/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh_topology_metadata.cpp.o [95/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/utils/conduit_utils_python.so [96/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/conduit_python.so [97/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh_flatten.cpp.o [98/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node.dir/t_conduit_node.cpp.o [99/130] Building CXX object tests/conduit_tests/CMakeFiles/t_conduit_node_set.dir/t_conduit_node_set.cpp.o [100/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh_partition.cpp.o [101/130] Building CXX object thirdparty/conduit/blueprint/CMakeFiles/catalyst_blueprint.dir/conduit_blueprint_mesh.cpp.o [102/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/blueprint/mcarray/conduit_blueprint_mcarray_python.so [103/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/blueprint/table/conduit_blueprint_table_python.so [104/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/blueprint/conduit_blueprint_python.so [105/130] Linking CXX shared library lib/libcatalyst.so.3 [106/130] Creating library symlink lib/libcatalyst.so [107/130] Linking CXX executable bin/test_catalyst_abi [108/130] Linking Fortran shared library lib/libcatalyst_fortran.so [109/130] Linking CXX executable bin/test_conduit_abi [110/130] Linking CXX shared module lib/python3.12/site-packages/catalyst_conduit/blueprint/mesh/conduit_blueprint_mesh_python.so [111/130] Linking CXX shared module lib/catalyst/libcatalyst-double.so [112/130] Linking CXX shared module lib/catalyst/libcatalyst-external_conduit.so [113/130] Linking CXX shared module lib/catalyst/libcatalyst-stub.so [114/130] Linking CXX shared module lib/catalyst/libcatalyst-internal_conduit.so [115/130] Linking C executable bin/test_catalyst_results [116/130] Linking CXX executable bin/test_catalyst_conduit [117/130] Linking C executable bin/test_external_conduit_impl [118/130] Linking C executable bin/test_double_impl [119/130] Linking C executable bin/test_internal_conduit_impl [120/130] Linking CXX executable bin/t_conduit_node_compare [121/130] Linking CXX executable bin/t_conduit_node_paths [122/130] Linking Fortran executable bin/test_double_impl_f [123/130] Linking CXX executable bin/t_conduit_node [124/130] Linking CXX executable bin/t_conduit_node_parent [125/130] Linking CXX executable bin/catalyst_replay [126/130] Linking CXX executable bin/t_conduit_node_info [127/130] Linking CXX executable bin/t_conduit_to_string [128/130] Linking CXX executable bin/t_conduit_node_to_value [129/130] Linking CXX executable bin/t_conduit_node_set [130/130] Linking CXX shared module lib/python3.12/site-packages/catalyst/catalyst_python.so ==> Starting check()... Internal ctest changing into directory: /startdir/src/build Test project /startdir/src/build Start 1: install-prepare Start 3: example-build-about-prepare Start 7: example-build-adaptor0-prepare Start 11: example-build-replay-prepare Start 35: test-build-replay_high_num_ranks-prepare Start 39: test-build-replay_ranks_mismatch-prepare Start 43: test-build-replay_high_num_execute_invc-prepare Start 47: test-build-replay_no_data_dump_dir-prepare 1/106 Test #1: install-prepare ............................................... Passed 0.01 sec 2/106 Test #3: example-build-about-prepare ................................... Passed 0.01 sec 3/106 Test #7: example-build-adaptor0-prepare ................................ Passed 0.01 sec Start 2: install Start 51: test-build-replay_missing_initialize_data-prepare Start 55: test-build-replay_missing_execute_invc-prepare 4/106 Test #35: test-build-replay_high_num_ranks-prepare ...................... Passed 0.01 sec 5/106 Test #11: example-build-replay-prepare .................................. Passed 0.01 sec Start 59: test-build-replay_high_num_ranks_fortran-prepare Start 63: test-build-replay_ranks_mismatch_fortran-prepare 6/106 Test #39: test-build-replay_ranks_mismatch-prepare ...................... Passed 0.01 sec 7/106 Test #43: test-build-replay_high_num_execute_invc-prepare ............... Passed 0.01 sec 8/106 Test #47: test-build-replay_no_data_dump_dir-prepare .................... Passed 0.01 sec Start 67: test-build-replay_high_num_execute_invc_fortran-prepare Start 71: test-build-replay_no_data_dump_dir_fortran-prepare Start 75: test-build-replay_missing_initialize_data_fortran-prepare 9/106 Test #51: test-build-replay_missing_initialize_data-prepare ............. Passed 0.01 sec 10/106 Test #55: test-build-replay_missing_execute_invc-prepare ................ Passed 0.01 sec 11/106 Test #59: test-build-replay_high_num_ranks_fortran-prepare .............. Passed 0.01 sec 12/106 Test #63: test-build-replay_ranks_mismatch_fortran-prepare .............. Passed 0.01 sec Start 79: test-build-replay_missing_execute_invc_fortran-prepare Start 83: test-build-replay_high_num_ranks_python-prepare Start 87: test-build-replay_ranks_mismatch_python-prepare Start 91: test-build-replay_high_num_execute_invc_python-prepare 13/106 Test #67: test-build-replay_high_num_execute_invc_fortran-prepare ....... Passed 0.01 sec 14/106 Test #71: test-build-replay_no_data_dump_dir_fortran-prepare ............ Passed 0.01 sec Start 95: test-build-replay_no_data_dump_dir_python-prepare Start 99: test-build-replay_missing_initialize_data_python-prepare 15/106 Test #75: test-build-replay_missing_initialize_data_fortran-prepare ..... Passed 0.01 sec Start 103: test-build-replay_missing_execute_invc_python-prepare 16/106 Test #79: test-build-replay_missing_execute_invc_fortran-prepare ........ Passed 0.01 sec Start 4: example-build-about 17/106 Test #83: test-build-replay_high_num_ranks_python-prepare ............... Passed 0.01 sec 18/106 Test #87: test-build-replay_ranks_mismatch_python-prepare ............... Passed 0.01 sec Start 5: example-install-about-prepare Start 8: example-build-adaptor0 19/106 Test #91: test-build-replay_high_num_execute_invc_python-prepare ........ Passed 0.01 sec 20/106 Test #95: test-build-replay_no_data_dump_dir_python-prepare ............. Passed 0.01 sec 21/106 Test #99: test-build-replay_missing_initialize_data_python-prepare ...... Passed 0.01 sec 22/106 Test #103: test-build-replay_missing_execute_invc_python-prepare ......... Passed 0.01 sec Start 9: example-install-adaptor0-prepare Start 12: example-build-replay Start 13: example-install-replay-prepare Start 15: catalyst-abi 23/106 Test #5: example-install-about-prepare ................................. Passed 0.01 sec Start 16: conduit-abi 24/106 Test #9: example-install-adaptor0-prepare .............................. Passed 0.01 sec 25/106 Test #15: catalyst-abi .................................................. Passed 0.00 sec Start 17: catalyst-abi-nm Start 18: catalyst-impl-double 26/106 Test #16: conduit-abi ................................................... Passed 0.00 sec Start 19: catalyst-results 27/106 Test #13: example-install-replay-prepare ................................ Passed 0.01 sec Start 20: catalyst-conduit 28/106 Test #18: catalyst-impl-double .......................................... Passed 0.05 sec 29/106 Test #19: catalyst-results .............................................. Passed 0.05 sec 30/106 Test #20: catalyst-conduit .............................................. Passed 0.05 sec Start 21: catalyst-impl-external-conduit Start 22: catalyst-impl-internal-conduit Start 23: test_conduit_import_python 31/106 Test #21: catalyst-impl-external-conduit ................................ Passed 0.05 sec 32/106 Test #22: catalyst-impl-internal-conduit ................................ Passed 0.05 sec Start 24: test_catalyst_import_python Start 25: test_double_impl_python 33/106 Test #17: catalyst-abi-nm ............................................... Passed 0.10 sec Start 26: catalyst-impl-double-fortran 34/106 Test #23: test_conduit_import_python .................................... Passed 0.09 sec Start 27: t_conduit_node 35/106 Test #26: catalyst-impl-double-fortran .................................. Passed 0.05 sec Start 28: t_conduit_node_compare 36/106 Test #27: t_conduit_node ................................................ Passed 0.05 sec Start 29: t_conduit_node_info 37/106 Test #28: t_conduit_node_compare ........................................ Passed 0.05 sec Start 30: t_conduit_node_parent 38/106 Test #25: test_double_impl_python ....................................... Passed 0.12 sec Start 31: t_conduit_node_paths 39/106 Test #24: test_catalyst_import_python ................................... Passed 0.13 sec Start 32: t_conduit_node_set 40/106 Test #29: t_conduit_node_info ........................................... Passed 0.05 sec Start 33: t_conduit_to_string 41/106 Test #30: t_conduit_node_parent ......................................... Passed 0.05 sec Start 34: t_conduit_node_to_value 42/106 Test #31: t_conduit_node_paths .......................................... Passed 0.05 sec Start 36: test-build-replay_high_num_ranks 43/106 Test #32: t_conduit_node_set ............................................ Passed 0.05 sec Start 37: test-install-replay_high_num_ranks-prepare 44/106 Test #33: t_conduit_to_string ........................................... Passed 0.05 sec Start 40: test-build-replay_ranks_mismatch 45/106 Test #37: test-install-replay_high_num_ranks-prepare .................... Passed 0.01 sec Start 41: test-install-replay_ranks_mismatch-prepare 46/106 Test #41: test-install-replay_ranks_mismatch-prepare .................... Passed 0.01 sec Start 44: test-build-replay_high_num_execute_invc 47/106 Test #34: t_conduit_node_to_value ....................................... Passed 0.05 sec Start 45: test-install-replay_high_num_execute_invc-prepare 48/106 Test #45: test-install-replay_high_num_execute_invc-prepare ............. Passed 0.01 sec Start 48: test-build-replay_no_data_dump_dir 49/106 Test #2: install ....................................................... Passed 0.51 sec Start 6: example-install-about 50/106 Test #4: example-build-about ........................................... Passed 1.31 sec Start 10: example-install-adaptor0 51/106 Test #8: example-build-adaptor0 ........................................ Passed 1.79 sec Start 14: example-install-replay 52/106 Test #6: example-install-about ......................................... Passed 1.97 sec Start 38: test-install-replay_high_num_ranks 53/106 Test #36: test-build-replay_high_num_ranks ..............................***Failed 2.36 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks ======== CMake output ====== CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Configuring done (0.8s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/5] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [2/5] Building CXX object CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_driver.cxx.o [3/5] Linking CXX executable high_num_ranks_driver [4/5] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [5/5] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.01 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/mpiexec "-n" "10" "/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/high_num_ranks_driver" "/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/catalyst" 2: Working Directory: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/high_num_ranks_driver 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.09 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /startdir/src/build/tests/replay_tests/build-replay_high_num_ranks/high_num_ranks_driver 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.10 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 42: test-install-replay_ranks_mismatch 54/106 Test #10: example-install-adaptor0 ...................................... Passed 2.10 sec Start 46: test-install-replay_high_num_execute_invc 55/106 Test #38: test-install-replay_high_num_ranks ............................***Failed 1.76 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks ======== CMake output ====== CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Configuring done (0.7s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/5] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [2/5] Building CXX object CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_driver.cxx.o [3/5] Linking CXX executable high_num_ranks_driver [4/5] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [5/5] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.01 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/mpiexec "-n" "10" "/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/high_num_ranks_driver" "/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/catalyst" 2: Working Directory: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/high_num_ranks_driver 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.04 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /startdir/src/build/tests/replay_tests/install-replay_high_num_ranks/high_num_ranks_driver 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.04 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 49: test-install-replay_no_data_dump_dir-prepare 56/106 Test #49: test-install-replay_no_data_dump_dir-prepare .................. Passed 0.01 sec Start 50: test-install-replay_no_data_dump_dir 57/106 Test #12: example-build-replay .......................................... Passed 4.88 sec Start 52: test-build-replay_missing_initialize_data 58/106 Test #44: test-build-replay_high_num_execute_invc ....................... Passed 4.70 sec Start 53: test-install-replay_missing_initialize_data-prepare 59/106 Test #53: test-install-replay_missing_initialize_data-prepare ........... Passed 0.01 sec Start 54: test-install-replay_missing_initialize_data 60/106 Test #40: test-build-replay_ranks_mismatch .............................. Passed 4.83 sec Start 56: test-build-replay_missing_execute_invc 61/106 Test #48: test-build-replay_no_data_dump_dir ............................ Passed 5.18 sec Start 57: test-install-replay_missing_execute_invc-prepare 62/106 Test #57: test-install-replay_missing_execute_invc-prepare .............. Passed 0.01 sec Start 58: test-install-replay_missing_execute_invc 63/106 Test #14: example-install-replay ........................................ Passed 4.58 sec Start 60: test-build-replay_high_num_ranks_fortran 64/106 Test #42: test-install-replay_ranks_mismatch ............................ Passed 4.09 sec Start 61: test-install-replay_high_num_ranks_fortran-prepare 65/106 Test #61: test-install-replay_high_num_ranks_fortran-prepare ............ Passed 0.01 sec Start 62: test-install-replay_high_num_ranks_fortran 66/106 Test #46: test-install-replay_high_num_execute_invc ..................... Passed 4.04 sec Start 64: test-build-replay_ranks_mismatch_fortran 67/106 Test #50: test-install-replay_no_data_dump_dir .......................... Passed 4.01 sec Start 65: test-install-replay_ranks_mismatch_fortran-prepare 68/106 Test #65: test-install-replay_ranks_mismatch_fortran-prepare ............ Passed 0.01 sec Start 66: test-install-replay_ranks_mismatch_fortran 69/106 Test #52: test-build-replay_missing_initialize_data ..................... Passed 4.28 sec Start 68: test-build-replay_high_num_execute_invc_fortran 70/106 Test #56: test-build-replay_missing_execute_invc ........................ Passed 4.17 sec Start 69: test-install-replay_high_num_execute_invc_fortran-prepare 71/106 Test #69: test-install-replay_high_num_execute_invc_fortran-prepare ..... Passed 0.02 sec Start 70: test-install-replay_high_num_execute_invc_fortran 72/106 Test #54: test-install-replay_missing_initialize_data ................... Passed 4.33 sec Start 72: test-build-replay_no_data_dump_dir_fortran 73/106 Test #58: test-install-replay_missing_execute_invc ...................... Passed 4.17 sec Start 73: test-install-replay_no_data_dump_dir_fortran-prepare 74/106 Test #73: test-install-replay_no_data_dump_dir_fortran-prepare .......... Passed 0.02 sec Start 74: test-install-replay_no_data_dump_dir_fortran 75/106 Test #60: test-build-replay_high_num_ranks_fortran ......................***Failed 3.76 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran ======== CMake output ====== CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done The Fortran compiler identification is GNU 14.2.1 Detecting Fortran compiler ABI info Detecting Fortran compiler ABI info - done Check for working Fortran compiler: /usr/bin/gfortran - skipped Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Found MPI_Fortran: /usr/lib/libmpi_usempif08.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: Fortran Configuring done (1.8s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/7] Building Fortran preprocessed CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/fortran/common_src_dir/common_replay_driver.F90-pp.f90 f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [2/7] Generating Fortran dyndep file CMakeFiles/high_num_ranks_driver.dir/Fortran.dd [3/7] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [4/7] Building Fortran object CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/fortran/common_src_dir/common_replay_driver.F90.o f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [5/7] Linking Fortran executable high_num_ranks_driver [6/7] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [7/7] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.01 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/mpiexec "-n" "10" "/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/high_num_ranks_driver" "/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/catalyst" 2: Working Directory: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/high_num_ranks_driver 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.19 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /startdir/src/build/tests/replay_tests/fortran/build-replay_high_num_ranks_fortran/high_num_ranks_driver 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.22 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 76: test-build-replay_missing_initialize_data_fortran 76/106 Test #62: test-install-replay_high_num_ranks_fortran ....................***Failed 3.79 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran ======== CMake output ====== CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done The Fortran compiler identification is GNU 14.2.1 Detecting Fortran compiler ABI info Detecting Fortran compiler ABI info - done Check for working Fortran compiler: /usr/bin/gfortran - skipped Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Found MPI_Fortran: /usr/lib/libmpi_usempif08.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: Fortran Configuring done (1.9s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/7] Building Fortran preprocessed CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/fortran/common_src_dir/common_replay_driver.F90-pp.f90 f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [2/7] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [3/7] Generating Fortran dyndep file CMakeFiles/high_num_ranks_driver.dir/Fortran.dd [4/7] Building Fortran object CMakeFiles/high_num_ranks_driver.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/fortran/common_src_dir/common_replay_driver.F90.o f951: Warning: command-line option ‘-Wformat=1’ is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: Warning: ‘-Werror=’ argument ‘-Werror=format-security’ is not valid for Fortran [5/7] Linking Fortran executable high_num_ranks_driver [6/7] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [7/7] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.01 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/mpiexec "-n" "10" "/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/high_num_ranks_driver" "/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/catalyst" 2: Working Directory: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/high_num_ranks_driver 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.22 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /startdir/src/build/tests/replay_tests/fortran/install-replay_high_num_ranks_fortran/high_num_ranks_driver 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.23 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 77: test-install-replay_missing_initialize_data_fortran-prepare 77/106 Test #77: test-install-replay_missing_initialize_data_fortran-prepare ... Passed 0.02 sec Start 78: test-install-replay_missing_initialize_data_fortran 78/106 Test #64: test-build-replay_ranks_mismatch_fortran ...................... Passed 8.19 sec Start 80: test-build-replay_missing_execute_invc_fortran 79/106 Test #66: test-install-replay_ranks_mismatch_fortran .................... Passed 9.65 sec Start 81: test-install-replay_missing_execute_invc_fortran-prepare 80/106 Test #81: test-install-replay_missing_execute_invc_fortran-prepare ...... Passed 0.01 sec Start 82: test-install-replay_missing_execute_invc_fortran 81/106 Test #68: test-build-replay_high_num_execute_invc_fortran ............... Passed 10.46 sec Start 84: test-build-replay_high_num_ranks_python 82/106 Test #70: test-install-replay_high_num_execute_invc_fortran ............. Passed 10.50 sec Start 85: test-install-replay_high_num_ranks_python-prepare 83/106 Test #85: test-install-replay_high_num_ranks_python-prepare ............. Passed 0.02 sec Start 86: test-install-replay_high_num_ranks_python 84/106 Test #74: test-install-replay_no_data_dump_dir_fortran .................. Passed 10.34 sec Start 88: test-build-replay_ranks_mismatch_python 85/106 Test #72: test-build-replay_no_data_dump_dir_fortran .................... Passed 10.71 sec Start 89: test-install-replay_ranks_mismatch_python-prepare 86/106 Test #89: test-install-replay_ranks_mismatch_python-prepare ............. Passed 0.02 sec Start 90: test-install-replay_ranks_mismatch_python 87/106 Test #78: test-install-replay_missing_initialize_data_fortran ........... Passed 9.85 sec Start 92: test-build-replay_high_num_execute_invc_python 88/106 Test #76: test-build-replay_missing_initialize_data_fortran ............. Passed 10.62 sec Start 93: test-install-replay_high_num_execute_invc_python-prepare 89/106 Test #93: test-install-replay_high_num_execute_invc_python-prepare ...... Passed 0.02 sec Start 94: test-install-replay_high_num_execute_invc_python 90/106 Test #86: test-install-replay_high_num_ranks_python .....................***Failed 4.17 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python ======== CMake output ====== The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Found Python3: /usr/bin/python3.12 (found version "3.12.7") found components: Interpreter Configuring done (2.2s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/3] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [2/3] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [3/3] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.02 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/cmake "-E" "env" "--modify" "PYTHONPATH=path_list_prepend:/startdir/src/build/root/usr/lib/cmake/catalyst-2.0/../../../lib/python3.12/site-packages" "/usr/bin/mpiexec" "-n" "10" "/usr/bin/python3.12" "/startdir/src/catalyst-v2.0.0/tests/replay_tests/python/common_src_dir/common_replay_driver.py" "/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/catalyst" "--use-mpi" 2: Working Directory: /startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/python/install-replay_high_num_ranks_python/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /usr/bin/python3.12 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.28 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /usr/bin/python3.12 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.30 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 96: test-build-replay_no_data_dump_dir_python 91/106 Test #84: test-build-replay_high_num_ranks_python .......................***Failed 4.47 sec Internal cmake changing into directory: /startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python ======== CMake output ====== The C compiler identification is GNU 14.2.1 The CXX compiler identification is GNU 14.2.1 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done Found MPI_C: /usr/lib/libmpi.so (found version "3.1") Found MPI: TRUE (found version "3.1") found components: C Found Python3: /usr/include/python3.12 (found version "3.12.7") found components: Development Development.Module Development.Embed Found Python3: /usr/bin/python3.12 (found version "3.12.7") found components: Interpreter Configuring done (2.2s) Generating done (0.0s) Build files have been written to: /startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python ======== End CMake output ====== Change Dir: '/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python' Run Clean Command: /usr/bin/ninja clean [1/1] Cleaning all built files... Cleaning... 0 files. Run Build Command(s): /usr/bin/ninja [1/3] Building C object CMakeFiles/high_num_ranks_adaptor.dir/catalyst_impl_replay.c.o [2/3] Building CXX object CMakeFiles/high_num_ranks_adaptor.dir/startdir/src/catalyst-v2.0.0/tests/replay_tests/common_src_dir/common_replay_adaptor.cxx.o [3/3] Linking CXX shared module catalyst/libcatalyst-replay.so Running test command: "/usr/bin/ctest" "-C" "$" "-V" "--output-on-failure" Test command failed: /usr/bin/ctest UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/DartConfiguration.tcl UpdateCTestConfiguration from :/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/DartConfiguration.tcl Parse Config file:/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/DartConfiguration.tcl Test project /startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: high_num_ranks_write_prepare 1: Test command: /usr/bin/cmake "-E" "rm" "-rf" "/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/data_dump/" 1: Working Directory: /startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python 1: Test timeout computed to be: 1500 1/3 Test #1: high_num_ranks_write_prepare ..... Passed 0.02 sec test 2 Start 2: high_num_ranks_write_out 2: Test command: /usr/bin/cmake "-E" "env" "--modify" "PYTHONPATH=path_list_prepend:/startdir/src/build/lib/cmake/catalyst-2.0/../../../lib/python3.12/site-packages" "/usr/bin/mpiexec" "-n" "10" "/usr/bin/python3.12" "/startdir/src/catalyst-v2.0.0/tests/replay_tests/python/common_src_dir/common_replay_driver.py" "/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/catalyst" "--use-mpi" 2: Working Directory: /startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python 2: Environment variables: 2: CATALYST_DATA_DUMP_DIRECTORY=/startdir/src/build/tests/replay_tests/python/build-replay_high_num_ranks_python/data_dump/ 2: Test timeout computed to be: 1500 2: -------------------------------------------------------------------------- 2: There are not enough slots available in the system to satisfy the 10 2: slots that were requested by the application: 2: 2: /usr/bin/python3.12 2: 2: Either request fewer procs for your application, or make more slots 2: available for use. 2: 2: A "slot" is the PRRTE term for an allocatable unit where we can 2: launch a process. The number of slots available are defined by the 2: environment in which PRRTE processes are run: 2: 2: 1. Hostfile, via "slots=N" clauses (N defaults to number of 2: processor cores if not provided) 2: 2. The --host command line parameter, via a ":N" suffix on the 2: hostname (N defaults to 1 if not provided) 2: 3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.) 2: 4. If none of a hostfile, the --host command line parameter, or an 2: RM is present, PRRTE defaults to the number of processor cores 2: 2: In all the above cases, if you want PRRTE to default to the number 2: of hardware threads instead of the number of processor cores, use the 2: --use-hwthread-cpus option. 2: 2: Alternatively, you can use the --map-by :OVERSUBSCRIBE option to ignore the 2: number of available slots when deciding the number of processes to 2: launch. 2: -------------------------------------------------------------------------- 2: 2/3 Test #2: high_num_ranks_write_out .........***Failed 0.20 sec -------------------------------------------------------------------------- There are not enough slots available in the system to satisfy the 10 slots that were requested by the application: /usr/bin/python3.12 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. -------------------------------------------------------------------------- test 3 Start 3: high_num_ranks_read_in Failed test dependencies: high_num_ranks_write_out 3/3 Test #3: high_num_ranks_read_in ...........***Not Run 0.00 sec 33% tests passed, 2 tests failed out of 3 Total Test time (real) = 0.22 sec The following tests FAILED: 2 - high_num_ranks_write_out (Failed) 3 - high_num_ranks_read_in (Not Run) Errors while running CTest CMake Error at /startdir/src/catalyst-v2.0.0/cmake/catalyst-test-path-setting.cmake:40 (message): test or example failed! Start 97: test-install-replay_no_data_dump_dir_python-prepare 92/106 Test #97: test-install-replay_no_data_dump_dir_python-prepare ........... Passed 0.02 sec Start 98: test-install-replay_no_data_dump_dir_python 93/106 Test #80: test-build-replay_missing_execute_invc_fortran ................ Passed 8.74 sec Start 100: test-build-replay_missing_initialize_data_python 94/106 Test #82: test-install-replay_missing_execute_invc_fortran .............. Passed 9.00 sec Start 101: test-install-replay_missing_initialize_data_python-prepare 95/106 Test #101: test-install-replay_missing_initialize_data_python-prepare .... Passed 0.02 sec Start 102: test-install-replay_missing_initialize_data_python 96/106 Test #88: test-build-replay_ranks_mismatch_python ....................... Passed 7.29 sec Start 104: test-build-replay_missing_execute_invc_python 97/106 Test #90: test-install-replay_ranks_mismatch_python ..................... Passed 7.81 sec Start 105: test-install-replay_missing_execute_invc_python-prepare 98/106 Test #94: test-install-replay_high_num_execute_invc_python .............. Passed 7.10 sec Start 106: test-install-replay_missing_execute_invc_python 99/106 Test #105: test-install-replay_missing_execute_invc_python-prepare ....... Passed 0.01 sec 100/106 Test #92: test-build-replay_high_num_execute_invc_python ................ Passed 7.50 sec 101/106 Test #96: test-build-replay_no_data_dump_dir_python ..................... Passed 6.71 sec 102/106 Test #98: test-install-replay_no_data_dump_dir_python ................... Passed 6.71 sec 103/106 Test #100: test-build-replay_missing_initialize_data_python .............. Passed 6.57 sec 104/106 Test #104: test-build-replay_missing_execute_invc_python ................. Passed 6.07 sec 105/106 Test #102: test-install-replay_missing_initialize_data_python ............ Passed 6.72 sec 106/106 Test #106: test-install-replay_missing_execute_invc_python ............... Passed 6.13 sec 94% tests passed, 6 tests failed out of 106 Label Time Summary: Python = 0.34 sec*proc (3 tests) Total Test time (real) = 34.05 sec The following tests FAILED: 36 - test-build-replay_high_num_ranks (Failed) 38 - test-install-replay_high_num_ranks (Failed) 60 - test-build-replay_high_num_ranks_fortran (Failed) 62 - test-install-replay_high_num_ranks_fortran (Failed) 84 - test-build-replay_high_num_ranks_python (Failed) 86 - test-install-replay_high_num_ranks_python (Failed) Errors while running CTest ==> ERROR: A failure occurred in check(). Aborting... ==> ERROR: Build failed, check /home/alhp/workspace/chroot/build_e4ea6541-4c1c-4cf8-a07d-d5d5bfc1d790/build