Hello. I have problem with running testsuite. Sometimes it's passes sometimes not. Below is the relevant output when it fail. If I run another time it succeeds. Very strange.
BTW, could anybody give me a hint, what shall I do after modification of incremental.at so that next run of ./testsuite took that modifications into account? Thank you. camobap tests # ./testsuite -x -d -v 26 ## ------------------------ ## ## GNU tar 1.19 test suite. ## ## ------------------------ ## 26. incremental.at:23: testing ... + set +x ./incremental.at:26: mkdir gnu (cd gnu TEST_TAR_FORMAT=gnu export TEST_TAR_FORMAT TAR_OPTIONS="-H gnu" export TAR_OPTIONS rm -rf * mkdir structure echo x >structure/file # On Nextstep (and perhaps other 4.3BSD systems), # a newly created file's ctime isn't updated # until the next sync or stat operation on the file. ls -l structure/file >/dev/null # If the time of an initial backup and the creation time of a file contained # in that backup are the same, the file will be backed up again when an # incremental backup is done, because the incremental backup backs up # files created `on or after' the initial backup time. Without the sleep # command, behaviour of tar becomes variable, depending whether the system # clock ticked over to the next second between creating the file and # backing it up. sleep 1 tar cf archive --listed=list structure tar cfv archive --listed=list structure echo separator sleep 1 echo y >structure/file tar cfv archive --listed=list structure ) Not enabling shell tracing (command contains an embedded newline) + set +x ./incremental.at:26: mkdir oldgnu (cd oldgnu TEST_TAR_FORMAT=oldgnu export TEST_TAR_FORMAT TAR_OPTIONS="-H oldgnu" export TAR_OPTIONS rm -rf * mkdir structure echo x >structure/file # On Nextstep (and perhaps other 4.3BSD systems), # a newly created file's ctime isn't updated # until the next sync or stat operation on the file. ls -l structure/file >/dev/null # If the time of an initial backup and the creation time of a file contained # in that backup are the same, the file will be backed up again when an # incremental backup is done, because the incremental backup backs up # files created `on or after' the initial backup time. Without the sleep # command, behaviour of tar becomes variable, depending whether the system # clock ticked over to the next second between creating the file and # backing it up. sleep 1 tar cf archive --listed=list structure tar cfv archive --listed=list structure echo separator sleep 1 echo y >structure/file tar cfv archive --listed=list structure ) Not enabling shell tracing (command contains an embedded newline) --- - 2007-11-20 19:54:27.119415829 +0300 +++ /var/tmp/portage/app-arch/tar-1.19-failed/work/tar-1.19/tests/testsuite.dir/at-stdout 2007-11-20 19:54:26.000000000 +0300 @@ -1,5 +1,4 @@ structure/ separator structure/ -structure/file 26. incremental.at:23: FAILED (incremental.at:26) ## ------------- ## ## Test results. ## ## ------------- ## ERROR: 1 test was run, 1 failed unexpectedly. ## -------------------------- ## ## testsuite.log was created. ## ## -------------------------- ## Please send `tests/testsuite.log' and all information you think might help: To: <[email protected]> Subject: [GNU tar 1.19] testsuite: 26 failed -- Peter.
