[sr #110989] Improve reliability of AT_MTIME_DELAY in test suite with a loop

Follow-up Comment #1, sr#110989 (group autoconf):

Zack, isn't that essentially the code you wrote for
_AM_FILESYSTEM_TIMESTAMP_RESOLUTION in Automake (sanity.m4)?


for am_try_res in $am_try_resolutions; do
  # Any one fine-grained sleep might happen to cross the boundary
  # between two values of a coarser actual resolution, but if we do
  # two fine-grained sleeps in a row, at least one of them will fall
  # entirely within a coarse interval.
  echo alpha > conftest.ts1
  sleep $am_try_res
  echo beta > conftest.ts2
  sleep $am_try_res
  echo gamma > conftest.ts3

  # We assume that 'ls -t' will make use of high-resolution
  # timestamps if the operating system supports them at all.
  if (set X `ls -t conftest.ts?` &&
      test "$[]2" = conftest.ts3 &&
      test "$[]3" = conftest.ts2 &&
      test "$[]4" = conftest.ts1); then
    am_cv_filesystem_timestamp_resolution=$am_try_res
    break
  fi
done




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110989>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/