search for: remote_client

Hi, I've looked into use of the remote variables: REMOTE_HOST, REMOTE_CLIENT, REMOTE_USER, etc. Can you tell me how exactly one uses these variables to run the llvm test-suite remotely? As far as I can tell, the local host and remote host directory structures have to match exactly. In addition, it seems that the remote host has to pre-generate building the test executab...

On Jan 27, 2010, at 3:42 PM, Jose Rangel wrote: > Hi, > > I’ve looked into use of the remote variables: REMOTE_HOST, REMOTE_CLIENT, REMOTE_USER, etc. Can you tell me how exactly one uses these variables to run the llvm test-suite remotely? > > As far as I can tell, the local host and remote host directory structures have to match exactly. In addition, it seems that the remote host has to pre-generate building the test...

...properly cross-compiled on your desktop and you want to run the unit tests automatically on an ARM board. Chrood might work, but I am looking for some option like <runremote.sh --host XXX --user ....>. I have seen something related to it in projects/test-suite/Makefile.programs (REMOTE_HOST, REMOTE_CLIENT, etc.), but I haven´t found more information about these options. Thanks in advance, --Raul -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121115/7c6d27e9/attachment.html>

I use variants on the following command: make -k TEST=simple ARCH=ARM TARGET_FLAGS="-arch armv7 -isysroot path-to-sdk -ccc-install-dir path-to-binutils" USE_REFERENCE_OUTPUT=1 REMOTE_HOST=localhost REMOTE_USER=root REMOTE_CLIENT=ssh REMOTE_PORT=10022 DISABLE_JIT=1 DISABLE_CBE=1 SMALL_PROBLEM_SIZE=1 TARGET_CC=path-to-clang TARGET_CXX=path-to-clang++ report That assumes key-based ssh authentication (so you don't get password prompted for every execution) and that the test suite directory is is mounted on the target at t...

Testing on arm-darwin outside of Apple is _complicated_. I had it partially working about two years ago. The general approach is to use rsh/ssh to remotely execute each test on the target, which outside of Apple requires jailbreaking. In the old test system, setting up REMOTE_CLIENT=ssh, REMOTE_PORT, etc. would automatically use ssh to run the tests. In lit, it looks like TestRunner.py has support for external shells that may be intended for this purpose; I can't tell. The test-suite and bugpoint code for working this way is still present. The problem with this setup is t...

On Thu, Oct 13, 2011 at 10:33 AM, Raja Venkateswaran <rajav at codeaurora.org> wrote: > I think we need a group of maintainers rather than a single maintainer given > the spectrum of ARM targets/ISAs/platforms required to support There have been a plethora of ARM Instruction Set Architecture variants over the years. Which ones do we expect LLVM to support right now, and which as-yet

Hi Raul, I've successfully run them over ssh using LNT without too much difficulty. There is documentation on getting started with the LNT system here: http://llvm.org/docs/lnt/quickstart.html. It doesn't specifically mention remote execution, but if you give the lnt command a "--help" option then there are a few reasonably self-explanatory options described (--remote,