mirror of
https://github.com/rclone/rclone.git
synced 2024-12-23 20:24:14 +08:00
6d6dc00abb
Before this change, bisync had no mechanism for "retrying" a file again next time, in the event of an unexpected and possibly temporary error. After this change, bisync is now essentially able to mark a file as needing to be rechecked next time. Bisync does this by keeping one prior listing on hand at all times. In a low-confidence situation, bisync can revert a given file row back to its state at the end of the last known successful sync, ensuring that any subsequent changes will be re-noticed on the next run. This can potentially be helpful for a dynamically changing file system, where files may be changing quickly while bisync is working with them.
34 lines
980 B
Plaintext
34 lines
980 B
Plaintext
test volatile
|
|
|
|
test initial bisync
|
|
bisync resync
|
|
|
|
test changed on both paths - file5 (file5R, file5L)
|
|
touch-glob 2001-01-02 {datadir/} file5R.txt
|
|
copy-as {datadir/}file5R.txt {path2/} file5.txt
|
|
touch-glob 2001-03-04 {datadir/} file5L.txt
|
|
copy-as {datadir/}file5L.txt {path1/} file5.txt
|
|
|
|
test bisync with 50 files created during - should ignore new files
|
|
test-func
|
|
bisync
|
|
|
|
test changed on both paths - file5 (file5R, file5L)
|
|
touch-glob 2001-01-02 {datadir/} file5R.txt
|
|
copy-as {datadir/}file5R.txt {path2/} file5.txt
|
|
touch-glob 2001-03-04 {datadir/} file5L.txt
|
|
copy-as {datadir/}file5L.txt {path1/} file5.txt
|
|
|
|
test next bisync - should now notice new files
|
|
test-func
|
|
bisync
|
|
|
|
test changed on both paths - file5 (file5R, file5L)
|
|
touch-glob 2001-01-02 {datadir/} file5R.txt
|
|
copy-as {datadir/}file5R.txt {path2/} file5.txt
|
|
touch-glob 2001-03-04 {datadir/} file5L.txt
|
|
copy-as {datadir/}file5L.txt {path1/} file5.txt
|
|
|
|
test next bisync - should be no changes except dummy
|
|
test-func
|
|
bisync |