1
0
mirror of git://git.sv.gnu.org/coreutils.git synced 2026-03-08 05:57:39 +02:00
Files
coreutils/tests/misc/timeout-parameters.sh
Stefano Lattarini 21b5147fd8 build: don't use recursive make for tests/ subdirectory
* Makefile.am (SUBDIRS): Remove 'tests'.
(include): The '$(top_srcdir)/tests/local.mk' file.
(check-root): Remove this convenience target, it's no longer needed
now that the "real" check-root target once in 'tests/Makefile' will
land in the top-level makefile.
* configure.ac (AC_CONFIG_FILES): Remove 'tests/Makefile'.
* tests/Makefile.am: Rename ...
* tests/local.mk: ... like this, with a lot of adjustments.
* tests/init.cfg: Move ...
* init.cfg: ... here.  This is necessary, for a limitation of the
gnulib-provided 'tests/init.sh', which unconditionally look for
'init.cfg' in the $(srcdir) directory.
* tests/*/*.sh: Adjust: expect init.sh to be in '$srcdir/tests',
not in '$srcdir', and extend $PATH with './src', not with '../src'.
* tests/Coreutils.pm: Adjust similarly.
* tests/pr/pr-tests.pl ($pfx): Likewise.
2012-09-05 08:48:29 +02:00

81 lines
2.1 KiB
Bash
Executable File

#!/bin/sh
# Validate timeout parameter combinations
# Copyright (C) 2008-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 3 of the License, 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/>.
. "${srcdir=.}/tests/init.sh"; path_prepend_ ./src
print_ver_ timeout
getlimits_
# internal errors are 125, distinct from execution failure
# invalid timeout
timeout invalid sleep 0
test $? = 125 || fail=1
# invalid kill delay
timeout --kill-after=invalid 1 sleep 0
test $? = 125 || fail=1
# invalid timeout suffix
timeout 42D sleep 0
test $? = 125 || fail=1
# It was seen on 32 bit Linux/HPPA that a kernel time_t overflowed,
# thus causing the timer to fire immediately.
# So verify that doesn't happen before checking large timeouts
KERNEL_OVERFLOW_LIMIT=$(expr $TIME_T_MAX - $(date +%s) + 100)
timeout $KERNEL_OVERFLOW_LIMIT sleep 0
if test $? != 124; then
# timeout overflow
timeout $UINT_OFLOW sleep 0
test $? = 0 || fail=1
# timeout overflow
timeout $(expr $UINT_MAX / 86400 + 1)d sleep 0
test $? = 0 || fail=1
# timeout overflow
timeout 999999999999999999999999999999999999999999999999999999999999d sleep 0
test $? = 0 || fail=1
# floating point notation
timeout 2.34e+5d sleep 0
test $? = 0 || fail=1
fi
# floating point notation
timeout 2.34 sleep 0
test $? = 0 || fail=1
# nanoseconds potentially supported
timeout .999999999 sleep 0 || fail=1
# invalid signal spec
timeout --signal=invalid 1 sleep 0
test $? = 125 || fail=1
# invalid command
timeout 10 .
test $? = 126 || fail=1
# no such command
timeout 10 no_such
test $? = 127 || fail=1
Exit $fail