E4S-Project / E4S-Project/testsuite

kokkos test failing

Open
#41 0 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

CDASH: https://my.cdash.org/test/63278698

buildspec: https://github.com/buildtesters/buildtest-nersc/blob/devel/buildspecs/e4s/E4S-Testsuite/perlmutter/22.05/kokkos.yml

+ make
[ 14%] Building CXX object CMakeFiles/example_no_kokkos.dir/bar.cpp.o
[ 28%] Linking CXX executable example_no_kokkos
[ 28%] Built target example_no_kokkos
[ 42%] Building CXX object CMakeFiles/example_with_kokkos.dir/foo.cpp.o
[ 57%] Linking CXX executable example_with_kokkos
[ 57%] Built target example_with_kokkos
Scanning dependencies of target example_cmake
[ 71%] Building CXX object CMakeFiles/example_cmake.dir/cmake_example.cpp.o
[ 85%] Building Fortran object CMakeFiles/example_cmake.dir/foo.f.o
[100%] Linking CXX executable example_cmake
[100%] Built target example_cmake
Running /global/cfs/cdirs/m3503/buildtest/runs/perlmutter_check/2022-09-28/perlmutter.slurm.regular/kokkos/kokkos_e4s_testsuite_22.05/9afbd51c/stage/testsuite/validation_tests/kokkos
Skipping load: Environment already setup
+ export OMP_PROC_BIND=spread
+ OMP_PROC_BIND=spread
+ export OMP_PLACES=threads
+ OMP_PLACES=threads
+ export OMP_NUM_THREADS=8
+ OMP_NUM_THREADS=8
+ ./build/example_with_kokkos 500000000
WARNING: Requested total thread count and/or thread affinity may result in
oversubscription of available CPU resources!  Performance may be degraded.
Explicitly set OMP_WAIT_POLICY=PASSIVE or ACTIVE to suppress this message.
Set CRAY_OMP_CHECK_AFFINITY=TRUE to print detailed thread-affinity messages.
terminate called after throwing an instance of 'std::runtime_error'
  what():  Kokkos::Impl::HostThreadTeamData::organize_pool ERROR pool already exists
./run.sh: line 7: 61519 Aborted                 ./build/example_with_kokkos 500000000
Run failed

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 buildspecs/e4s/E4S-Testsuite/perlmutter/22.05/kokkos.yml and the linked CDASH result. Reproduce the failure by running ./build/example_with_kokkos 500000000 in the kokkos validation test, then investigate the Kokkos HostThreadTeamData error. Done means the validation test completes without the pool-already-exists runtime error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.