[LLVMdev] test-suite RunSafely.sh remote execution with test copy

James Courtier-Dutton james.dutton at gmail.com
Fri Aug 15 23:29:37 PDT 2014


On Aug 15, 2014 10:37 PM, "Brian M. Rzycki" <brzycki at gmail.com> wrote:
>
> Hello everyone,
>
> I am working to run the LLVM Nightly Testsuite on embedded arm devices.
Not all of these devices can mount NFS to share a common directory tree. To
mitigate this I have patched test-suite/RunSafely.sh (attached) to create a
temporary directory, run the test remotely, collect the output, and cleanup
after itself. The patch breaks compatibility with the current remote device
model in the following ways:
>
> 1. uses scp/rcp to copy files from the host running test-suite instead of
assuming an identical tree on the remote device.
> 2. expects the remote device to have the mktemp command to create the
temporary workspace (usually under /tmp/*)
> 3. expects the remote device to have timeit installed in its path. If
timeit were compiled statically I could scp the one passed into
RunSafely.sh to the destination. Hosts with a different libc than the
tested compiler (Android, embedded uClibc devices) cannot run the
dynamically-linked timeit.
> 4. It's a bit slower due to all the network copies for the entire test
suite.
>
> I'd appreciate feedback and suggestions as to how I can rework this model
for inclusion upstream. I'm sure there are others out there that would find
this kind of testing useful. I'm fine with a new remote-copy mode that can
be passed in via lnt nt command line invocation.
>
> I hope others find this useful.
> -Brian

Have you tried sshfs.
I does much the same as nfs mount but uses ssh instead.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140816/813d7d54/attachment.html>


More information about the llvm-dev mailing list