diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2010-10-15 21:52:40 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2010-10-15 21:53:37 -0700 |
| commit | 502abd93bd8bfba15677aceb221c4530d257bbab (patch) | |
| tree | 1d99613b2310fe46a37dc49269574821531ddf00 /tests/rename05.at | |
| parent | 241b72ffadc9128f5fe2d2fc8d9cf3ff5e23f57a (diff) | |
| download | tar-502abd93bd8bfba15677aceb221c4530d257bbab.tar.gz | |
tests: port to NFS file servers with clock skew
Several of the tests assumed that a newly created file cannot
have a time stamp dated in the future. This assumption is not
true when files are served by a remote host whose clock is
slightly in advance of ours. Fix the problems that I observed
when running "make check" a couple of times on such a server.
* tests/backup01.at: Use --warning=no-timestamp to suppress
clock-skew warnings.
* tests/chtype.at, tests/comprec.at, tests/exclude06.at:
* tests/extrac01.at, tests/extrac03.at, tests/extrac05.at:
* tests/extrac06.at, tests/extrac08.at, tests/extrac13.at:
* tests/extrac14.at, tests/incr01.at, tests/incr03.at, tests/link01.at:
* tests/multiv01.at, tests/multiv02.at, tests/multiv03.at:
* tests/pipe.at, tests/rename02.at, tests/rename03.at:
* tests/rename05.at, tests/same-order01.at, tests/same-order02.at:
* tests/sparse01.at:
Likewise.
Diffstat (limited to 'tests/rename05.at')
| -rw-r--r-- | tests/rename05.at | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/rename05.at b/tests/rename05.at index 26d92024..54a9067a 100644 --- a/tests/rename05.at +++ b/tests/rename05.at @@ -46,11 +46,11 @@ tar -cf archive.2 -g db.2 dir mv dir orig decho First restore -tar -xf archive.1 -g db.1 +tar -xf archive.1 -g db.1 --warning=no-timestamp find directory | sort decho Second restore -tar -xf archive.2 -g db.2 +tar -xf archive.2 -g db.2 --warning=no-timestamp find dir | sort ], [0], |