Files
swift-mirror/test/remote-run/dry-run.test-sh
Alastair Houghton 2f6f051f75 Use rsync for remote-run.
Not only does this give us a huge speed-up, it also works around a problem
where sftp doesn't always update the modification time, which causes random
test failures.

rdar://88179140
2022-02-01 19:21:23 +00:00

24 lines
860 B
Plaintext

REQUIRES: shell
RUN: %empty-directory(%t)
RUN: %debug-remote-run -n --input-prefix %S/Inputs/ ls %S/Inputs/upload/1.txt %S/Inputs/upload/2.txt 2>&1 >/dev/null | %FileCheck -check-prefix CHECK-INPUT %s
RUN: test -z "`ls %t`"
RUN: test ! -e %t-REMOTE
CHECK-INPUT: /usr/bin/env /bin/mkdir -p {{.+}}-REMOTE/input
CHECK-INPUT-NEXT: /usr/bin/rsync
CHECK-INPUT: /usr/bin/env {{.*}}ls
RUN: %empty-directory(%t)
RUN: %empty-directory(%t/nested)
RUN: touch %t/nested/input %t/nested/BAD
RUN: %debug-remote-run -n --output-prefix %t cp %t/nested/input %t/nested/output 2>&1 >/dev/null | %FileCheck -check-prefix CHECK-OUTPUT %s
RUN: test ! -e %t-REMOTE
CHECK-OUTPUT: /usr/bin/env /bin/mkdir -p {{.+}}-REMOTE/output/nested
CHECK-OUTPUT: /usr/bin/rsync
CHECK-OUTPUT: /usr/bin/env {{.*}}cp
CHECK-OUTPUT-NEXT: {{^}}/bin/mkdir -p {{.+}}
CHECK-OUTPUT-NEXT: /usr/bin/rsync