1. 23 Feb, 2019 8 commits
    • Thomas Haller's avatar
      release: update NEWS · 6c1c59d5
      Thomas Haller authored
    • Thomas Haller's avatar
    • Thomas Haller's avatar
    • Thomas Haller's avatar
      release: update NEWS · efbd2928
      Thomas Haller authored
    • Thomas Haller's avatar
    • Thomas Haller's avatar
      Revert "build/meson: name platform tests like autotools" · 5551b3ab
      Thomas Haller authored
      Older versions of meson don't support building the same names
      multiple times.
        Meson encountered an error in file src/tests/meson.build, line 14, column 2:
        Tried to create target "test-general", but a target of that name already exists.
      We really need to use unique filenames everywhere. Revert the name
      change for now.
      This breaks again the valgrind workaround in "tools/run-nm-test.sh".
      This reverts commit 5466edc6.
    • Thomas Haller's avatar
      build/meson: name platform tests like autotools · 5466edc6
      Thomas Haller authored
      Meson and autotools should name the tests the same way.
      Also, all tests binaries built by autotools start on purpose
      with "test-". Do that for meson too.
      Also, otherwise "tools/run-nm-test.sh" fails to workaround
      valgrind failures for platform tests as it does not expect
      the tests to be named that way:
          if [ $HAS_ERRORS -eq 0 ]; then
              # valgrind doesn't support setns syscall and spams the logfile.
              # hack around it...
              if [ "$TEST_NAME" = 'test-link-linux' -o \
                   "$TEST_NAME" = 'test-acd' ]; then
                  if [ -z "$(sed -e '/^--[0-9]\+-- WARNING: unhandled .* syscall: /,/^--[0-9]\+-- it at http.*\.$/d' "$LOGFILE")" ]; then
    • Thomas Haller's avatar
      build/meson: increase timeouts for some tests · b1f6d53b
      Thomas Haller authored
      The defaults for test timeouts in meson is 30 seconds. That is not long
      enough when running
        $ NMTST_USE_VALGRIND=1 ninja -C build test
      Note that meson supports --timeout-multiplier, and automatically
      increases the timeout when running under valgrind. However, meson
      does not understand that we are running tests under valgrind via
      NMTST_USE_VALGRIND=1 environment variable.
      Timeouts are really not expected to be reached and are a mean of last
      resort. Hence, increasing the timeout to a large value is likely to
      have no effect or to fix test failures where the timeout was too rigid.
      It's unlikely that the test indeed hangs and the increase of timeout
      causes a unnecessary increase of waittime before aborting.
  2. 22 Feb, 2019 32 commits