Skip to content

[Bug] Errors in DeePMD and PEXSI unit tests #7593

Description

@ZhouXY-PKU

Describe the bug

  1. DeePMD
CMakeFiles/MODULE_ESOLVER_esolver_dp_test.dir/__/esolver_dp.cpp.o: In function `deepmd::hpp::DeepBaseModel::get_type_map(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)':
deepmd-kit-3.1.0/include/deepmd/deepmd.hpp:940: undefined reference to `DP_DeepBaseModelGetTypeMap'
  1. PEXSI
source/source_hsolver/test/diago_pexsi_test.cpp(388): error: function "PexsiPrepare<T>::PexsiPrepare(const PexsiPrepare<double> &) [with T=double]" (declared implicitly) cannot be referenced -- it is a deleted function
      PexsiPrepare<double> dp = GetParam();
                                ^
/usr/include/c++/8/tuple(1468): error: no instance of constructor "std::tuple<_Elements...>::tuple [with _Elements=<testing::internal::ValueArray<PexsiPrepare<double>, PexsiPrepare<double>>>]" matches the argument list
            argument types are: (testing::internal::ValueArray<PexsiPrepare<double>, PexsiPrepare<double>>)
        return __result_type(std::forward<_Elements>(__args)...);
               ^
source/source_hsolver/test/diago_pexsi_test.cpp(139): error: identifier "descinit_" is undefined
          descinit_(hmtest.desc, &nlocal, &nlocal, &nb2d, &nb2d, &ISRC, &ISRC, &icontxt, &(hmtest.nrow), &info);
          ^
          detected during:
            instantiation of "void PexsiPrepare<T>::pb2d() [with T=double]" at line 234
            instantiation of "void PexsiPrepare<T>::diago() [with T=double]" at line 407

Expected behavior

No response

To Reproduce

No response

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

  • Verify the issue is not a duplicate.
  • Describe the bug.
  • Steps to reproduce.
  • Expected behavior.
  • Error message.
  • Environment details.
  • Additional context.
  • Assign a priority level (low, medium, high, urgent).
  • Assign the issue to a team member.
  • Label the issue with relevant tags.
  • Identify possible related issues.
  • Create a unit test or automated test to reproduce the bug (if applicable).
  • Fix the bug.
  • Test the fix.
  • Update documentation (if necessary).
  • Close the issue and inform the reporter (if applicable).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions