Skip to content
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions test/CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@
# See https://llvm.org/LICENSE.txt for license information.
#
##===----------------------------------------------------------------------===##
enable_testing()
Copy link

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This call to enable_testing() is redundant. The root CMakeLists.txt already calls enable_testing() at line 357 before adding the test subdirectory via add_subdirectory(test) at line 358. Since enable_testing() propagates to all subdirectories, tests in test/kt/ and other subdirectories are already enabled by the root-level call. While this redundant call is harmless (enable_testing() is idempotent), it doesn't provide any additional functionality.

Suggested change
enable_testing()

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already existing call of enable_testing() at

enable_testing()
is not enough at least for MS Visual Studio 2026 to see built tests list in Test Explorer.

Copy link
Copy Markdown
Contributor

@dmitriy-sobolev dmitriy-sobolev Feb 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's then remove enable_testing from the root directory and keep it here.

I think it will be closer to what enable_testing expects according to its documentation:

This command should be invoked in the top-level source directory because ctest(1) expects to find a test file in the top-level build directory.

The cmake puts executables into test subdirectory.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I got confused by this cmake note.

Indeed, our cmake will place tests inside test directory, but I now think that the right way is to place it inside the top-level CMakeLists after investigating the sources of other different projects, e.g. see oneTBB, OpenCV or JSON. Perhaps, we should change where add_test should put the files, or there is a bug in VS2026 and we should do it only for this configuration. Let me think about it...


add_subdirectory(kt)

# rng_tests
Expand Down