kc3-lang/automake/tests/test-driver-fail.test

• Show log

  Commit

• Hash : db973eaa
  Author :
  Date : 2012-02-21T19:47:36
  

  tests: prefer 'configure.ac' over 'configure.in'
  
  With this change, our testsuite now uses 'configure.ac' as the
  name for the typical autoconf input, instead of the obsolescent
  'configure.in' (which has been deprecated for several years, at
  least since autoconf 2.50).
  
  Most of the test cases changed by this commit have been
  automatically modified with this sed command (using GNU
  sed):
  
    sed -i 's/\<configure\(\\\?\)\.in\>/configure\1.ac/g'
  
  * syntax-checks.mk (sc_tests_no_configure_in): New syntax check.
  (syntax_check_rules): Add it.
  * tests/defs: Create stub for autoconf input in 'configure.ac',
  not in 'configure.in'.  Adjust comments.
  ($AUTOCONF, $AUTOHEADER, $AUTORECONF): Remove workaround for the
  infamous debian autoconf wrapper: we don't need such workaround
  anymore now that we name our autoconf input as 'configure.ac'.
  For more information, see commit v1.11-564-g63da492 "test defs:
  hack to support autoconf-wrapper programs" of 16-12-2011.
  * tests/README: Use 'configure.ac', not 'configure.in'.
  * Many many tests: Likewise.
  * tests/backcompat3.test: Adjust to avoid spurious failures.
  * tests/backcompat5.test: Likewise.
  * tests/missing6.test: Likewise.
  * tests/backcompat6.test: Likewise, and extend a bit since we
  are at it.
  

Download

• tests/test-driver-fail.test

• #! /bin/sh
  # Copyright (C) 2011-2012 Free Software Foundation, Inc.
  #
  # This program is free software; you can redistribute it and/or modify
  # it under the terms of the GNU General Public License as published by
  # the Free Software Foundation; either version 2, or (at your option)
  # any later version.
  #
  # This program is distributed in the hope that it will be useful,
  # but WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  # GNU General Public License for more details.
  #
  # You should have received a copy of the GNU General Public License
  # along with this program.  If not, see <http://www.gnu.org/licenses/>.
  
  # Custom test drivers: what happens when a test driver fails?  Well,
  # "make check" should at least fail too, and the test-suite.log
  # shouldn't be created.  Unfortunately, we cannot truly control also
  # the (non-)creation of individual test logs, since those are expected
  # to be created by the drivers themselves, and an ill-behaved driver
  # (like our dummy one in this test) might leave around a test log even
  # in case of internal failures.
  
  am_parallel_tests=yes
  . ./defs || Exit 1
  
  cat >> configure.ac <<'END'
  AC_OUTPUT
  END
  
  cat > Makefile.am <<'END'
  TEST_LOG_DRIVER = ./oops
  TESTS = foo.test
  END
  
  cat > foo.test <<'END'
  #! /bin/sh
  exit 0
  END
  
  $ACLOCAL
  $AUTOCONF
  $AUTOMAKE
  
  ./configure
  
  # The testsuite driver does not exist.
  $MAKE check && Exit 1
  test ! -f test-suite.log
  
  # The testsuite driver exists and create the test log files, but fails.
  
  cat > oops <<'END'
  #!/bin/sh
  : > foo.log
  echo 'Oops, I fail!' >&2
  exit 1
  END
  chmod a+x oops
  
  $MAKE check && Exit 1
  test ! -f test-suite.log
  
  :
  

Download