Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.0.23: build with`BUILD_TESTS=ON` and no ctest units found

See original GitHub issue

Looks like something is wrong with test suite. cmake configuration

[tkloczko@devel-g2v x86_64-redhat-linux-gnu]$ cmake -L
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


CMake Error: The source directory "/home/tkloczko/rpmbuild/BUILD/OpenXR-SDK-Source-release-1.0.23/x86_64-redhat-linux-gnu" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
-- Cache values
BASH_COMMAND:FILEPATH=/usr/bin/bash
BUILD_ALL_EXTENSIONS:BOOL=ON
BUILD_API_LAYERS:BOOL=ON
BUILD_FORCE_GENERATION:BOOL=OFF
BUILD_LOADER:BOOL=ON
BUILD_LOADER_WITH_EXCEPTION_HANDLING:BOOL=ON
BUILD_SPECIFICATION:BOOL=OFF
BUILD_TESTS:BOOL=ON
BUILD_WITH_STD_FILESYSTEM:BOOL=OFF
BUILD_WITH_SYSTEM_JSONCPP:BOOL=ON
BUILD_WITH_WAYLAND_HEADERS:BOOL=ON
BUILD_WITH_XCB_HEADERS:BOOL=ON
BUILD_WITH_XLIB_HEADERS:BOOL=ON
CMAKE_BUILD_TYPE:STRING=RelWithDebInfo
CMAKE_INSTALL_PREFIX:PATH=/usr
DYNAMIC_LOADER:BOOL=ON
FALLBACK_CONFIG_DIRS:STRING=/etc/xdg
FALLBACK_DATA_DIRS:STRING=/usr/local/share:/usr/share
GLSLANG_VALIDATOR:FILEPATH=/usr/bin/glslangValidator
GLSL_COMPILER:FILEPATH=/usr/bin/glslc
OPENXR_DEBUG_POSTFIX:STRING=
PRESENTATION_BACKEND:STRING=xlib

And with those settings:

[tkloczko@devel-g2v x86_64-redhat-linux-gnu]$ ctest -vv
Test project /home/tkloczko/rpmbuild/BUILD/OpenXR-SDK-Source-release-1.0.23/x86_64-redhat-linux-gnu
No tests were found!!!

There is no test suite? 🤔

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

rpavlikcommented, Jun 13, 2022

OK, looks like we don’t actually have the add_test calls to enable ctest: there are tests but not wired up that way. We are manually changing into the loader_test directory and running it. (The other “tests” in the source tree aren’t exactly tests but more sample/demo apps or compile tests.)

The absence of include(CTest) (except in vendored source trees) should be an indication to you that we don’t have ctest support in the build system yet.

0reactions

rpavlik-botcommented, Jun 15, 2022

An issue (number 1733) has been filed to correspond to this issue in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#1733 ), to facilitate working group processes.

This GitHub issue will continue to be the main site of discussion.

Top Results From Across the Web

What does the ctest error "no tests were found" exactly mean?

When running ctest, I get the following error message: Test project /home/path_to_my_project/build No tests were found!!!

Unit tests not run during build · Issue #23 · conda-forge/scikit ...

Although the recipe has the logic to run the unit tests via sys.exit(skimage.test(verbose=True)) , the unit tests are not run during the build....

ctest(1) — CMake 3.25.1 Documentation

The ctest executable is the CMake test driver program. CMake-generated build trees created for projects that use the enable_testing() and add_test() ...

Unit Testing — QMCPACK Manual documentation

All of the tests in each tests directory get compiled into an executable. After building the project, the individual unit test executables can...

JEDI Testing — JEDI Documentation 1 documentation

You can also run the executable test files directly, without going through ctest. To do this, first find the executable in the build...