The existing test fragments in the CMake files had two undesirable effects:
1. Projects using Graphviz as a subdirectory would pick up this test suite and
it would get run as part of their own test suite. See #1795.
2. The fragments incorrectly gave the impression this was the canonical set of
Graphviz tests and/or that this is what was run in CI. The current reality
is that CI ignores this path to a subset of the tests, and most of the
maintainers do not run this either.
- Autotools build system support for eFence has been removed
- Building Graphviz with ICC defaults to -O2 instead of -O0
- Build system work arounds for GCC 3 have been removed
+- Incomplete support for running the test suite under CMake has been removed
### Fixed
- gvpr: line numbers in gvpr errors/warnings are incorrect #1594
add_subdirectory(plugin)
add_subdirectory(cmd)
-enable_testing()
-add_subdirectory(tests)
MATH(EXPR GRAPHVIZ_PLUGIN_VERSION "${GRAPHVIZ_PLUGIN_VERSION}+1")
set(GVPLUGIN_VERSION "${GRAPHVIZ_PLUGIN_VERSION}")
set(VERSION "${GRAPHVIZ_VERSION_STRING}")
+++ /dev/null
-find_package(PythonInterp)
-
-if (PYTHONINTERP_FOUND)
- add_subdirectory(regression_tests)
-else ()
- message(WARNING "Python interperter not found, required for regression tests.")
-endif ()
+++ /dev/null
-add_subdirectory(shapes)
-
-#### vuln tests cause appveyor build fails because reference is not the same for all os/dist - disabled
-# add_subdirectory(vuln)
+++ /dev/null
-add_test(
- NAME shapes
- WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}"
- COMMAND ${PYTHON_EXECUTABLE} shapes.py
-)
+++ /dev/null
-add_test(
- NAME vuln
- WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}"
- COMMAND ${PYTHON_EXECUTABLE} vuln.py
-)