summaryrefslogtreecommitdiff
path: root/tools/run-nm-test.sh
Commit message (Collapse)AuthorAgeFilesLines
* all: goodbye libnm-glibLubomir Rintel2019-04-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* Revert "all: goodbye libnm-glib"Lubomir Rintel2019-04-031-1/+1
| | | | | | We need this for a little little longer :( This reverts commit 1de8383ad9fdfc8f552117e5d109bdfa7005634b.
* all: goodbye libnm-glibLubomir Rintel2019-03-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* acd/tests: skip NAcd tests under valgrindThomas Haller2018-10-041-2/+5
| | | | | | | | | | | | | | Under valgrind, we cannot create an NAcd instance. --10916-- WARNING: unhandled amd64-linux syscall: 321 --10916-- You may be able to write your own handler. --10916-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --10916-- Nevertheless we consider this a bug. Please report --10916-- it at http://valgrind.org/support/bug_reports.html. This limitation already poses a problem, because running NetworkManager under valgrind might fail. However, for tests it doesn't matter and we can just skip them.
* docs: misc. typos pt2luz.paz2018-09-171-1/+1
| | | | | | | | | | | | | | | | | | | | | Remainder of typos found using `codespell -q 3 --skip="./shared,./src/systemd,*.po" -I ../NetworkManager-word-whitelist.txt` whereby whitelist consists of: ``` ans busses cace cna conexant crasher iff liftime creat nd sav technik uint ``` https://github.com/NetworkManager/NetworkManager/pull/205
* build: set LD_LIBRARY_PATH and GI_TYPELIB_PATH variables in run-nm-test.shThomas Haller2018-05-111-0/+29
| | | | | | | | | | With autotools, we use libtool so that the right libraries are automatically found. Still, we won't find the right GI typelib. Add a mechanism so that when make/meson invokes the run-nm-test.sh runner, it passes the build-root directory. Also, try to autodetect when invoked manually.
* build: meson: use run-nm-test.sh to run testsBeniamino Galvani2018-04-121-1/+6
| | | | | Like autotools, use the wrapper script 'run-nm-test.sh' that starts a separate D-Bus session when needed.
* tools/run-nm-test.sh: add -d option to set NMTST_DEBUG=dThomas Haller2018-04-091-0/+8
| | | | | For convenience, by passing "-d" to tools/run-nm-test.sh, we set NMTST_DEBUG=d (if $NMTST_DEBUG is unset previously).
* tests: accept trailing arguments to "tools/run-nm-test.sh"Thomas Haller2017-03-021-3/+11
| | | | | | | | | | | | | | | | | | | | | | | Previously, the test runner would only accept leading options, an optional "--" separator, followed by "$TEST" and optional arguments for the test. Like ./tools/run-nm-test.sh -m src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh That is annoying, because to toggle an option you have to seek the curser in the before the test name. Now, accept a "--test" option, so that the above can be done with trialing arguments: ./tools/run-nm-test.sh -t src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh -m However, the arguments for the tests still must come last: ./tools/run-nm-test.sh -m [--] src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh -p /settings/plugins/ifcfg-rh/bridge/write-master ./tools/run-nm-test.sh -t src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh -m [--] -p /settings/plugins/ifcfg-rh/bridge/write-master
* tests: fix "tools/run-nm-test.sh" to build test firstThomas Haller2017-03-021-8/+8
| | | | | | | | ./tools/run-nm-test.sh -m src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh makes the test before running it. However, that failed if the test didn't exist already. Reorder the code so that we always try to make the test before trying to run it.
* tests: improve run-nm-test.sh to weak valgrind usageThomas Haller2016-12-141-29/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | - also when called from makefile, allow enabling valgrind even if it was not enabled via configure option. That is, even if you configured --without-valgrind, you can run tests via `NMTST_USE_VALGRIND=1 make check`. Previously, there was no way to run on valgrind during `make check` unless you also had configured --with-valgrind. - Use $NMTST_VALGRIND variable to override the valgrind path. This now always takes precedence. For `make check`, the path can be determined by the configure script. If all unspecified, as last fallback "valgrind" is searched in the current $PATH. - Allow to specify the suppressions file via $NMTST_SUPPRESSIONS. If unset, fall back to the default. The default during `make check` is determined by the configure options. The default for manual invocation is our one valgrind.suppressions file. To use no suppressions file, set NMTST_SUPPRESSIONS to empty. Now, regardless of what you enabled during ./configure, you can overwrite it via: $ NMTST_USE_VALGRIND=1 \ NMTST_VALGRIND=~/bin/valgrind \ NMTST_SUPPRESSIONS=my-suppressions \ make check
* build: generate src/NetworkManager.ver during buildThomas Haller2016-11-101-1/+1
| | | | | | | | | | This adds 0.4 seconds to the build time. You can disable it by setting $NM_BUILD_NO_CREATE_EXPORTS environment variable. This is useful in the unexpected case that the script is broken. Or, if you just want to use a different, non-generated version-script. Or, if you want to save 0.4 seconds build-time.
* tests: fix run-nm-test.sh to use valgrind when --called-from-makeThomas Haller2016-11-101-8/+24
| | | | Fixes: dbafd2ce5094a9754df2c604a1bedc838fe334f2
* tools: improve handling arguments to run-nm-test.shThomas Haller2016-11-011-13/+31
| | | | | | | - add _is_true function so that user can set argument environment variables to yes|y|1 etc. - fix NMTST_CHANGE_DIRECTORY
* tools: improve --make-first option of test runner to handle relative test pathsThomas Haller2016-11-011-8/+12
| | | | | | | | | | | | With --make-first|-m we first call `make` on the test. However, the make path must be a relative path rooted in the top directory. Make sure we `cd` into the parent directory first and pass the proper make path. cd src ../tools/run-nm-test.sh -m settings/plugins/ifcfg-rh/tests/test-ifcfg-rh
* tools: add option to test runner to build test before running itThomas Haller2016-11-011-2/+11
| | | | ./tools/run-nm-test.sh -m src/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh
* tools: improve controlling whether to run run-nm-test.sh with valgrindThomas Haller2016-11-011-8/+21
| | | | | | Use new environment variable NMTST_USE_VALGRIND. It works both from `make check` and during explicit invocation of the test runner.
* build: merge "libnm/tests/Makefile.am" into toplevel MakefileThomas Haller2016-10-191-18/+22
|
* tests: combine "run-test-valgrind.sh" and "run-test-dbus-session.sh" in ↵Thomas Haller2016-10-191-0/+179
"run-nm-test.sh" No need to have two test-runners. Combine them, and call tests always via "tools/run-nm-test.sh". Yes, this brings an overhead, that we now always invoke the test with a test wrapper script, also --without-vagrind. Previously, that was only necessary for libnm tests that require their own D-Bus session. Later we will do non-recursive Makefiles, thus all tests should have the same LOG_COMPILER.
View Lorry Controller Status