On Apr 17, 2012, at 11:41 AM, Ross Gardler wrote: > Tests fail using SVN head on windows (both cygwin and cmd shell tested): > > mvn clean install > > gives > > org.apache.airavata.core.gfac.exception.ProviderException: Cannot run program > "/ > bin/echo" (in directory "\tmp"): CreateProcess error=2, The system cannot > find t > he file specified > at > org.apache.airavata.core.gfac.provider.impl.LocalProvider.executeAppl > ication(LocalProvider.java:212) > at > org.apache.airavata.core.gfac.provider.AbstractProvider.execute(Abstr > actProvider.java:68) > at > org.apache.airavata.core.gfac.services.impl.AbstractSimpleService.exe > cute(AbstractSimpleService.java:118) > at > org.apache.airavata.core.gfac.services.impl.PropertiesBasedServiceImp > lTest.testExecute(PropertiesBasedServiceImplTest.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > ----- > > mvn clean install -DSkipTests works > Since Jenkins is not reporting a problem I assume this is a windows > issue. Anyone else seeing it? Am I doing something wrong or should I > raise an issue?
Hi Ross, Glad to see you are building and running the tests. The short answer is this is known behavior on windows but lets brainstorm how we should handle it. Lets me first explain whats happening. As the core feature of Airavata is to wrap a command line applications and create web service/workflows for these applications. So in a multi-tiered scenario, there is XBaya GUI client running interacting with Airavata web services which communicate with computational resources. For executions, the commands are forked, executed through ssh on remote clusters, or go through the middleware for grid and cloud executions. This particular test case is assuming all are running on one machine so starting up the airavata services and attempting to run command line application locally. The failure shows, * All the components are built correctly, * An application is registered with "/bin/echo" as the path to the binary (turns out to be a bad assumption) * Create a workflow for this wrapped application service and execute it. * The execution fails trying to fork the command /bin/echo. Since /bin/echo is not accessible on a windows machine it fails, so the question are: Should we explicitly state that Airavata does not support windows at all? I am open to hearing community input here. Second alternative is, we take a stand that Airavata web services can be deployed on windows machines but cannot use the windows box to run applications. Third alternative is, support windows applications through cygwin. Once we get some discussion and community input, please raise an issue, either the features have to added or documentation has to be fixed and exit out of this error gracefully. Thanks, Suresh > > Ross > > > -- > Ross Gardler (@rgardler) > Programme Leader (Open Development) > OpenDirective http://opendirective.com
