E4S-Project / E4S-Project/testsuite

Pumi test fails on perlmutter

Open
#51 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Fortran
Stars
21
Forks
33
Avg merge
3m
Merged PRs (30d)
1

Description

@cwsmith

The spack test for this variant of pumi installed on perlmutter by e4s 22.11:

-- linux-sles15-zen3 / gcc@11.2.0 -------------------------------
pumi@2.2.7~fortran~int64~ipo~shared+simmodsuite_version_check~testing~zoltan build_system=cmake build_type=RelWithDebInfo simmodsuite=none

Fails with the following console output:

==> Error: TestFailure: 2 tests failed.


Command exited with status 127:
    './uniform' '../testdata/pipe.dmg' '../testdata/pipe.smb' 'pipe_unif.smb'
./uniform: error while loading shared libraries: libfabric.so.1: cannot open shared object file: No such file or directory



1 error found in test log:
     1    ==> Testing package pumi-2.2.7-llomhac
     2    ==> [2022-11-21-12:25:41.390040] testing pumi uniform mesh refinement
     3    ==> [2022-11-21-12:25:41.390483] './uniform' '../testdata/pipe.dmg' '../testdata/pipe.smb' 'pipe_unif.smb'
     4    ./uniform: error while loading shared libraries: libfabric.so.1: cannot open shared object file: No such file or directory
     5    FAILED: Command exited with status 127:
     6        './uniform' '../testdata/pipe.dmg' '../testdata/pipe.smb' 'pipe_unif.smb'
  >> 7    ./uniform: error while loading shared libraries: libfabric.so.1: cannot open shared object file: No such file or directory
     8    
     9      File "/global/cfs/cdirs/m3896/shared/ParaTools/E4S/22.11/PrgEnv-gnu/spack/bin/spack", line 100, in <module>



Failed to find executable '/opt/cray/pe/mpich/8.1.17/ofi/gnu/9.1/bin/mpiexec'

/global/cfs/cdirs/m3896/shared/ParaTools/E4S/22.11/PrgEnv-gnu/spack/lib/spack/spack/package_base.py:2023, in run_test:
       2020                    # We're below the package context, so get context from
       2021                    # stack instead of from traceback.
       2022                    # The traceback is truncated here, so we can't use it to
  >>   2023                    # traverse the stack.
       2024                    m = "\n".join(spack.build_environment.get_package_context(tb))
       2025
       2026                exc = e  # e is deleted after this block


/global/cfs/cdirs/m3896/shared/ParaTools/E4S/22.11/PrgEnv-gnu/spack/lib/spack/spack/build_environment.py:1086, in _setup_pkg_and_run:
       1083        tb_string = traceback.format_exc()
       1084
       1085        # build up some context from the offending package so we can
  >>   1086        # show that, too.
       1087        package_context = get_package_context(tb)
       1088
       1089        logfile = None

See test log for details:
  /pscratch/sd/w/wspear/perlmutter/spack_user_cache/test/hyjemf5zrzgrnmfmzuddmljbsxwuyat4/pumi-2.2.7-llomhac-test-out.txt

==> Error: 1 test(s) in the suite failed.

--- ==> Spack test hyjemf5zrzgrnmfmzuddmljbsxwuyat4
==> Testing package pumi-2.2.7-llomhac
======================== 1 failed, 0 passed of 1 specs ========================= ---

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Spack test log and the failing './uniform' test command for pumi 2.2.7 on perlmutter. Check why libfabric.so.1 is unavailable and why the recorded mpiexec path cannot be found. Done means the pumi test suite completes successfully for this perlmutter variant.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, fortran
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.