Skip to content

OpenMPI 5.0.1-3 Installation Failure #12282

Open
@vorlkets

Description

@vorlkets

I’m installing OpenMPI 5.0.1-3 (https://aur.archlinux.org/packages/openmpi-ucx) on Archlinux 6.7.1 (GCC 13.2.1-3, CUDA 11.1 11.1.1-3) on Dell Poweredge T620. Everything goes well till (No issue on Archlinux 6.7.0 (GCC 13.2.1-3 CUDA 12.3.1-2) on Dell Precision M6800):

Making check in datatype
make[2]: Entering directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make  opal_datatype_test unpack_hetero checksum position position_noncontig ddt_test ddt_raw ddt_raw2 unpack_ooo ddt_pack external32 large_data partial to_self reduce_local
make[3]: Entering directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
  CCLD     opal_datatype_test
  CCLD     unpack_hetero
  CCLD     checksum
  CCLD     position
  CCLD     position_noncontig
  CCLD     ddt_test
  CCLD     ddt_raw
  CCLD     ddt_raw2
  CCLD     unpack_ooo
  CCLD     ddt_pack
  CCLD     external32
  CCLD     large_data
  CCLD     partial
  CCLD     to_self
  CCLD     reduce_local
make[3]: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make  check-TESTS
make[3]: Entering directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make[4]: Entering directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
../../config/test-driver: line 112: 1380808 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: opal_datatype_test
PASS: unpack_hetero
../../config/test-driver: line 112: 1380857 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: checksum
../../config/test-driver: line 112: 1380884 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: position
../../config/test-driver: line 112: 1380916 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: position_noncontig
../../config/test-driver: line 112: 1380944 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: ddt_test
../../config/test-driver: line 112: 1380975 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: ddt_raw
PASS: ddt_raw2
PASS: unpack_ooo
../../config/test-driver: line 112: 1381044 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: ddt_pack
../../config/test-driver: line 112: 1381070 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: external32
PASS: large_data
../../config/test-driver: line 112: 1381120 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: partial
============================================================================
Testsuite summary for Open MPI 5.0.1
============================================================================
# TOTAL: 13
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  9
# XPASS: 0
# ERROR: 0
============================================================================
See test/datatype/test-suite.log
Please report to https://www.open-mpi.org/community/help/
============================================================================
make[4]: *** [Makefile:2012: test-suite.log] Error 1
make[4]: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make[3]: *** [Makefile:2120: check-TESTS] Error 2
make[3]: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make[2]: *** [Makefile:2277: check-am] Error 2
make[2]: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test/datatype'
make[1]: *** [Makefile:1416: check-recursive] Error 1
make[1]: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1/test'
make: *** [Makefile:1533: check-recursive] Error 1
make: Leaving directory '/home/vorlket/build/openmpi-ucx/src/openmpi-5.0.1'
==> ERROR: A failure occurred in check().
    Aborting...

Please describe the system on which you are running

  • Operating system/version:
  • Computer hardware:
  • Network type:

Details of the problem

Please describe, in detail, the problem that you are having, including the behavior you expect to see, the actual behavior that you are seeing, steps to reproduce the problem, etc. It is most helpful if you can attach a small program that a developer can use to reproduce your problem.

Note: If you include verbatim output (or a code block), please use a GitHub Markdown code block like below:

shell$ mpirun -n 2 ./hello_world

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions