Mercurial > hg
view tests/testlib/wait-on-file @ 46325:e5e6282fa66a
hghave: split apart testing for the curses module and `tic` executable
ef771d329961 skipped the check for the `tic` executable, because the curses
module alone on Windows is enough to pass the `test-*-curses.t` tests. However,
`test-status-color.t` uses this same check and explicitly invoked the
executable, which fails on Windows. From the cursory searching I did, curses on
unix requires `tic`, which I assume is why they were tied together in the first
place. So this continues to require both to get past the curses guards on non
Windows platforms.
Differential Revision: https://phab.mercurial-scm.org/D9814
author | Matt Harbison <matt_harbison@yahoo.com> |
---|---|
date | Sun, 17 Jan 2021 22:25:15 -0500 |
parents | 9d7d53771e5f |
children | a68b37524d50 |
line wrap: on
line source
#!/bin/sh # # wait up to TIMEOUT seconds until a WAIT_ON_FILE is created. # # In addition, this script can create CREATE_FILE once it is ready to wait. if [ $# -lt 2 ] || [ $# -gt 3 ]; then echo $# echo "USAGE: $0 TIMEOUT WAIT_ON_FILE [CREATE_FILE]" fi timer="$1" # Scale the timeout to match the sleep steps below, i.e. 1/0.02. timer=$(( 50 * $timer )) # If the test timeout have been extended, also scale the timer relative # to the normal timing. if [ "$HGTEST_TIMEOUT_DEFAULT" -lt "$HGTEST_TIMEOUT" ]; then timer=$(( ( $timer * $HGTEST_TIMEOUT) / $HGTEST_TIMEOUT_DEFAULT )) fi wait_on="$2" create="" if [ $# -eq 3 ]; then create="$3" fi if [ -n "$create" ]; then touch "$create" create="" fi while [ "$timer" -gt 0 ] && [ ! -f "$wait_on" ]; do timer=$(( $timer - 1)) sleep 0.02 done if [ "$timer" -le 0 ]; then echo "file not created after $1 seconds: $wait_on" >&2 exit 1 fi