Files
swift-mirror/test/remote-run/dry-run-remote.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

23 lines
1.1 KiB
Plaintext

RUN: %remote-run -n --remote-dir /xyz-REMOTE --input-prefix %S/Inputs/ some_user@some_host ls %S/Inputs/upload/1.txt %S/Inputs/upload/2.txt 2>&1 >/dev/null | %FileCheck -check-prefix CHECK-INPUT %s
CHECK-INPUT: /usr/bin/ssh -n some_user@some_host -- '/usr/bin/env' '/bin/mkdir' '-p' '{{.+}}-REMOTE/input'
CHECK-INPUT-NEXT: /usr/bin/rsync
CHECK-INPUT-SAME: some_user@some_host
CHECK-INPUT: /usr/bin/ssh -n some_user@some_host -- '/usr/bin/env' {{.*}}'ls'
RUN: %empty-directory(%t)
RUN: %empty-directory(%t/nested)
RUN: touch %t/nested/input %t/nested/BAD
RUN: %remote-run -n --remote-dir /xyz-REMOTE --output-prefix %/t some_user@some_host cp %/t/nested/input %/t/nested/output 2>&1 >/dev/null | %FileCheck -check-prefix CHECK-OUTPUT %s
CHECK-OUTPUT: /usr/bin/ssh -n some_user@some_host -- '/usr/bin/env' '/bin/mkdir' '-p' '{{.+}}-REMOTE/output'
CHECK-OUTPUT-NEXT: /usr/bin/rsync
CHECK-OUTPUT-SAME: some_user@some_host
CHECK-OUTPUT: /usr/bin/ssh -n some_user@some_host -- '/usr/bin/env' {{.*}}'cp'
CHECK-OUTPUT-NEXT: {{^}}/bin/mkdir -p {{.+}}
CHECK-OUTPUT-NEXT: /usr/bin/rsync
CHECK-OUTPUT-SAME: some_user@some_host