search for: remoterunsafely

Hello Evan, Thanks for looking at the patch. > This should use std::cerr and make sure it is wrapped inside the DEBUG > macro. Will do. > Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. > Can you move it to test-suite? Are you planning to change the llvm > test suite makefile to make use of RemoteRunSafely.sh? I thought about bugpoint remote mode and the RemoteRunSafely.sh script more as a manual tool rather than a part of the test suit....

...te client. Bugpoint should not be aware of any details how the test program will be delivered to a remote target, get executed there, and how the result of execution will be returned back to the host. So, it expects the "remote client" - whatever it is - take care of those 3 things. The RemoteRunSafely.sh does all these by using ssh. Viktor ----- Original Message ----- From: "Evan Cheng" <evan.cheng at apple.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Wednesday, July 08, 2009 1:33 PM Subject: Re: [LLVMdev] [PATCH] Fix for bugpoint -rem...

...not be aware of any details how the test program > will be delivered to a remote target, get executed there, and how > the result of execution will be returned back to the host. > So, it expects the "remote client" - whatever it is - take care of > those 3 things. > The RemoteRunSafely.sh does all these by using ssh. Alright. But then the script probably should be named bugpoint_rexec.sh or something. Also, can you enhance it so it supports ssh (also takes a -p option)? Chris, what do you think? I am not crazy about it living under tools/ bugpoint. But I don't see a mo...

On Jul 8, 2009, at 12:42 AM, Viktor Kutuzov wrote: > Hello Evan, > > Thanks for looking at the patch. > >> This should use std::cerr and make sure it is wrapped inside the >> DEBUG >> macro. > > Will do. > >> Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. >> Can you move it to test-suite? Are you planning to change the llvm >> test suite makefile to make use of RemoteRunSafely.sh? > > > I thought about bugpoint remote mode and the RemoteRunSafely.sh > script more as a manual tool rather than...

Thanks Viktor. + std::cout << "<run locally>" << std::flush; This should use std::cerr and make sure it is wrapped inside the DEBUG macro. Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. Can you move it to test-suite? Are you planning to change the llvm test suite makefile to make use of RemoteRunSafely.sh? Thanks, Evan On Jul 7, 2009, at 4:32 PM, Viktor Kutuzov wrote: > Hello everyone, > > Please find the patch attached. > This f...

Hello everyone, Please find the patch attached. This fixes the bugpoint -remote-client and adds a helper script for a remote run. -Viktor -------------- next part -------------- A non-text attachment was scrubbed... Name: ToolRunner.diff Type: application/octet-stream Size: 4210 bytes Desc: not available URL:

David, Please find attached 2 diffs. Please notice that RemoteRunSafely.sh may get moved to the test suite sub-tree. We have targeted different areas fso far which is great. What's your plan? I have been thinking of using -run-custom and -safe-run-custom argumants for the cross-tools to keep bugpoint out of knowing any target details ans such. Best regards, Vik...

...going on with that, perhaps something in the makefile hierarchy is setting PWD to /bin/pwd instead of executing that command to get the pwd. I will investigate. David On Jul 10, 2009, at 1:45 PM, Viktor Kutuzov wrote: > David, > > Please find attached 2 diffs. Please notice that RemoteRunSafely.sh > may get moved to the test suite sub-tree. > > We have targeted different areas fso far which is great. > What's your plan? > > I have been thinking of using -run-custom and -safe-run-custom > argumants for the cross-tools to keep bugpoint out of knowing any >...

Hi Viktor, I did not see your patches, can you send them again. Here are the changes that I have made that seem to get remote execution working for bugpoint. I have not yet changed the test system to provide -remote- client and -remote-port. David -------------- next part -------------- A non-text attachment was scrubbed... Name: patch2 Type: application/octet-stream Size: 1906 bytes Desc:

...file hierarchy is setting > PWD to /bin/pwd instead of executing that command to get the pwd. I > will investigate. > > David > > > On Jul 10, 2009, at 1:45 PM, Viktor Kutuzov wrote: > >> David, >> >> Please find attached 2 diffs. Please notice that RemoteRunSafely.sh >> may get moved to the test suite sub-tree. >> >> We have targeted different areas fso far which is great. >> What's your plan? >> >> I have been thinking of using -run-custom and -safe-run-custom >> argumants for the cross-tools to keep bugpoin...