packages: Remove the tests-dev packageWe don't want a tests-dev package, because this means set-devel dependson tests-dev, which transitively depends on tests, which means you can'tinstall set-de
packages: Remove the tests-dev packageWe don't want a tests-dev package, because this means set-devel dependson tests-dev, which transitively depends on tests, which means you can'tinstall set-devel without also getting tests.The only real "dev" files in tests-dev are from ATF (libprivateatf),so move that to its own package and add a dependency from tests.Also move Kyua to its own package, since this might be useful forrunning tests even when the user doesn't want the whole set of basetests installed.Add a dependency from -tests to both -atf and -kyua, and a dependencyon -set-base, since the tests won't work without the full base systeminstalled.The remaining "dev" files in tests are actually test artifacts, not realdevelopment libraries. Add a new NO_DEV_PACKAGE option to bsd.lib.mk,which causes dev files to be installed in the base package instead ofcreating a -dev package, and set this option for everything thatinstalls test libraries.While here, add a slightly more informative description for the testspackage.MFC after: 3 secondsReviewed by: bapt, emasteDifferential Revision: https://reviews.freebsd.org/D52597
show more ...
src: Use gnu++17 as the default C++ standardPreviously the compiler's default C++ standard was used unlike C wherebsd.sys.mk explicitly sets a default language version. Setting anexplicit defaul
src: Use gnu++17 as the default C++ standardPreviously the compiler's default C++ standard was used unlike C wherebsd.sys.mk explicitly sets a default language version. Setting anexplicit default version will give a more uniform experience acrossdifferent compilers and compiler versions.gnu++17 was chosen to match the default C standard. It is wellsupported by a wide range of clang (5+) and GCC (9+) versions.gnu++17 is also the default C++ standard in recent versions of clang(16+) and GCC (11+). As a result, many of the explicit CXXSTDsettings in Makefiles had the effect of lowering the C++ standardinstead of raising it as was originally intended and are removed.Note that the remaining explicit CXXSTD settings for atf and liblutokexplicitly lower the standard to C++11 due to use of the deprecatedauto_ptr<> template which is removed in later versions.Reviewed by: imp, asomers, dim, emasteDifferential Revision: https://reviews.freebsd.org/D49223
Update Makefile.depend filesAfter building packages we have a number of newand updated Makefile.depend filesReviewed by: stevek
atf_pytest_wrapper: fix use with pytest-7.4As of pytest 7.4 it no longer walks all the way to the root directoryof the file system to find conftest files. As a result we don't find /usr/tests/con
atf_pytest_wrapper: fix use with pytest-7.4As of pytest 7.4 it no longer walks all the way to the root directoryof the file system to find conftest files. As a result we don't find /usr/tests/conftest.py, and don't load atf_python. That in turn causesatf_python tests to fail.Explicitly set the confcutdir, as advised by the pytest changelog.See also: https://github.com/pytest-dev/pytest/pull/11043MFC after: 3 weeksSponsored by: Orange Business ServicesDifferential Revision: https://reviews.freebsd.org/D41064
atf_pytest_wrapper: fix pytest output truncationPass `-vv` to pytest in order to always get the full output.While here, enforce the modeline.Differential Revision: https://reviews.freebsd.org/D3
atf_pytest_wrapper: fix pytest output truncationPass `-vv` to pytest in order to always get the full output.While here, enforce the modeline.Differential Revision: https://reviews.freebsd.org/D37894MFC after: 2 weeks
testing: provide meaningful error when pytest is not availableatf format does not provide any way of signalling any error message back to the atf runner when listing tests. Work this around by re
testing: provide meaningful error when pytest is not availableatf format does not provide any way of signalling any error message back to the atf runner when listing tests. Work this around by reporting "__test_cases_list_pytest_binary_not_found__" test instead.Reviewed By: kpDifferential Revision: https://reviews.freebsd.org/D35721
testing: pass ATF vars to pytest via env instead of arguments.This change is a continuation of 9c42645a1e4d workaround.Apparently pytest argument parser is not happy when parsing values with spac
testing: pass ATF vars to pytest via env instead of arguments.This change is a continuation of 9c42645a1e4d workaround.Apparently pytest argument parser is not happy when parsing values with spaces or just more than one --atf-var argument.Switch wrapper to send these kv pairs as env variables. Specifically, use _ATF_VAR_key=value format to distinguish from the other vars.Add the `atf_vars` fixture returning all passed kv pairs as a dict.Reviewed by: lwhsuDifferential Revision: https://reviews.freebsd.org/D35625MFC after: 2 weeks
testing: workaround pytest parser bug in pytest-atf-wrapper.Reviewed by: lwhsu, kpDifferential Revision: https://reviews.freebsd.org/D35614MFC after: 2 weeks
testing: move atf-pytest-wrapper to /usr/libexecMove pytest wrapper to the collection of the other atf wrappers in libexec. It solves the problem of combining bits & pieces from bsd.test.mk and b
testing: move atf-pytest-wrapper to /usr/libexecMove pytest wrapper to the collection of the other atf wrappers in libexec. It solves the problem of combining bits & pieces from bsd.test.mk and bgs.prog.mk to address "test binary, but not the suite binary".Reviewed by: kpDifferential Revision: https://reviews.freebsd.org/D35604MFC after: 2 weeks