Re: Virtualenv setup issues on new machine
I think gradle is complaining that the path can't be found. Is there more information if you run it with --info? On Thu, Feb 28, 2019, 14:35 Ankur Goenka wrote: > Hi Beamers, > > I am trying build python sdk from a fresh git checkout on a new linux > machine but the setupVirtualEnv task is failing with the error below. The > complete build scan is at > https://scans.gradle.com/s/h3jwzeg5aralk/failure?openFailures=WzBd&openStackTraces=WzQsM10#top=0 > > From the error it seems that gradle is trying to find the virtualenv > command in beam/python folder. > I am able to run virtualenv from the bash directly and PATH seems to be > setup correctly. > > Anypointers about what might be happening? > > > org.gradle.api.tasks.TaskExecutionException > : > Execution failed for task ':beam-sdks-python:setupVirtualenv'. > Open stacktrace > Caused by: > org.gradle.process.internal.ExecException > : > A problem occurred starting process 'command 'virtualenv'' > Open stacktrace > Caused by: > net.rubygrapefruit.platform.NativeException > : > Could not start 'virtualenv' > Open stacktrace > Caused by: > java.io.IOException > : > Cannot run program "virtualenv" (in directory > "/tmp/beam/beam/sdks/python"): error=2, No such file or directory > Close stacktrace > at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start > (DefaultProcessLauncher.java:25) > at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start > (WrapperProcessLauncher.java:36) > at org.gradle.process.internal.ExecHandleRunner.run > (ExecHandleRunner.java:67) > at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. > run(CurrentBuildOperationPreservingRunnable.java:42) > at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. > onExecute(ExecutorPolicy.java:63) > at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run > (ManagedExecutorImpl.java:46) > at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. > run(ThreadFactoryImpl.java:55) > Caused by: > java.io.IOException > : > error=2, No such file or directory > Close stacktrace > at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start > (DefaultProcessLauncher.java:25) > at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start > (WrapperProcessLauncher.java:36) > at org.gradle.process.internal.ExecHandleRunner.run > (ExecHandleRunner.java:67) > at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. > run(CurrentBuildOperationPreservingRunnable.java:42) > at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. > onExecute(ExecutorPolicy.java:63) > at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run > (ManagedExecutorImpl.java:46) > at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. > run(ThreadFactoryImpl.java:55) > smime.p7s Description: S/MIME Cryptographic Signature
Re: Virtualenv setup issues on new machine
The issue seems to be with "." in the virtualenv path. virtualenv works after moving from "/usr/local/google/home/goenka/.local/bin" to "/usr/bin" On Thu, Feb 28, 2019 at 2:57 PM Udi Meiri wrote: > I think gradle is complaining that the path can't be found. > Is there more information if you run it with --info? > > On Thu, Feb 28, 2019, 14:35 Ankur Goenka wrote: > >> Hi Beamers, >> >> I am trying build python sdk from a fresh git checkout on a new linux >> machine but the setupVirtualEnv task is failing with the error below. The >> complete build scan is at >> https://scans.gradle.com/s/h3jwzeg5aralk/failure?openFailures=WzBd&openStackTraces=WzQsM10#top=0 >> >> From the error it seems that gradle is trying to find the virtualenv >> command in beam/python folder. >> I am able to run virtualenv from the bash directly and PATH seems to be >> setup correctly. >> >> Anypointers about what might be happening? >> >> >> org.gradle.api.tasks.TaskExecutionException >> : >> Execution failed for task ':beam-sdks-python:setupVirtualenv'. >> Open stacktrace >> Caused by: >> org.gradle.process.internal.ExecException >> : >> A problem occurred starting process 'command 'virtualenv'' >> Open stacktrace >> Caused by: >> net.rubygrapefruit.platform.NativeException >> : >> Could not start 'virtualenv' >> Open stacktrace >> Caused by: >> java.io.IOException >> : >> Cannot run program "virtualenv" (in directory >> "/tmp/beam/beam/sdks/python"): error=2, No such file or directory >> Close stacktrace >> at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start >> (DefaultProcessLauncher.java:25) >> at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start >> (WrapperProcessLauncher.java:36) >> at org.gradle.process.internal.ExecHandleRunner.run >> (ExecHandleRunner.java:67) >> at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable >> .run(CurrentBuildOperationPreservingRunnable.java:42) >> at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. >> onExecute(ExecutorPolicy.java:63) >> at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run >> (ManagedExecutorImpl.java:46) >> at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable >> .run(ThreadFactoryImpl.java:55) >> Caused by: >> java.io.IOException >> : >> error=2, No such file or directory >> Close stacktrace >> at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start >> (DefaultProcessLauncher.java:25) >> at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start >> (WrapperProcessLauncher.java:36) >> at org.gradle.process.internal.ExecHandleRunner.run >> (ExecHandleRunner.java:67) >> at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable >> .run(CurrentBuildOperationPreservingRunnable.java:42) >> at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. >> onExecute(ExecutorPolicy.java:63) >> at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run >> (ManagedExecutorImpl.java:46) >> at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable >> .run(ThreadFactoryImpl.java:55) >> >
Re: Virtualenv setup issues on new machine
Weird. Is that a known bug? On Thu, Feb 28, 2019 at 3:19 PM Ankur Goenka wrote: > The issue seems to be with "." in the virtualenv path. > virtualenv works after moving from > "/usr/local/google/home/goenka/.local/bin" to "/usr/bin" > > On Thu, Feb 28, 2019 at 2:57 PM Udi Meiri wrote: > >> I think gradle is complaining that the path can't be found. >> Is there more information if you run it with --info? >> >> On Thu, Feb 28, 2019, 14:35 Ankur Goenka wrote: >> >>> Hi Beamers, >>> >>> I am trying build python sdk from a fresh git checkout on a new linux >>> machine but the setupVirtualEnv task is failing with the error below. The >>> complete build scan is at >>> https://scans.gradle.com/s/h3jwzeg5aralk/failure?openFailures=WzBd&openStackTraces=WzQsM10#top=0 >>> >>> From the error it seems that gradle is trying to find the virtualenv >>> command in beam/python folder. >>> I am able to run virtualenv from the bash directly and PATH seems to be >>> setup correctly. >>> >>> Anypointers about what might be happening? >>> >>> >>> org.gradle.api.tasks.TaskExecutionException >>> : >>> Execution failed for task ':beam-sdks-python:setupVirtualenv'. >>> Open stacktrace >>> Caused by: >>> org.gradle.process.internal.ExecException >>> : >>> A problem occurred starting process 'command 'virtualenv'' >>> Open stacktrace >>> Caused by: >>> net.rubygrapefruit.platform.NativeException >>> : >>> Could not start 'virtualenv' >>> Open stacktrace >>> Caused by: >>> java.io.IOException >>> : >>> Cannot run program "virtualenv" (in directory >>> "/tmp/beam/beam/sdks/python"): error=2, No such file or directory >>> Close stacktrace >>> at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start >>> (DefaultProcessLauncher.java:25) >>> at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start >>> (WrapperProcessLauncher.java:36) >>> at org.gradle.process.internal.ExecHandleRunner.run >>> (ExecHandleRunner.java:67) >>> at >>> org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. >>> run(CurrentBuildOperationPreservingRunnable.java:42) >>> at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. >>> onExecute(ExecutorPolicy.java:63) >>> at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run >>> (ManagedExecutorImpl.java:46) >>> at >>> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. >>> run(ThreadFactoryImpl.java:55) >>> Caused by: >>> java.io.IOException >>> : >>> error=2, No such file or directory >>> Close stacktrace >>> at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start >>> (DefaultProcessLauncher.java:25) >>> at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start >>> (WrapperProcessLauncher.java:36) >>> at org.gradle.process.internal.ExecHandleRunner.run >>> (ExecHandleRunner.java:67) >>> at >>> org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. >>> run(CurrentBuildOperationPreservingRunnable.java:42) >>> at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. >>> onExecute(ExecutorPolicy.java:63) >>> at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run >>> (ManagedExecutorImpl.java:46) >>> at >>> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. >>> run(ThreadFactoryImpl.java:55) >>> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Virtualenv setup issues on new machine
Not sure, dog seems to be the only meaningful difference in 2 scenarios. On Thu, Feb 28, 2019 at 8:04 PM Udi Meiri wrote: > Weird. Is that a known bug? > > On Thu, Feb 28, 2019 at 3:19 PM Ankur Goenka wrote: > >> The issue seems to be with "." in the virtualenv path. >> virtualenv works after moving from >> "/usr/local/google/home/goenka/.local/bin" to "/usr/bin" >> >> On Thu, Feb 28, 2019 at 2:57 PM Udi Meiri wrote: >> >>> I think gradle is complaining that the path can't be found. >>> Is there more information if you run it with --info? >>> >>> On Thu, Feb 28, 2019, 14:35 Ankur Goenka wrote: >>> Hi Beamers, I am trying build python sdk from a fresh git checkout on a new linux machine but the setupVirtualEnv task is failing with the error below. The complete build scan is at https://scans.gradle.com/s/h3jwzeg5aralk/failure?openFailures=WzBd&openStackTraces=WzQsM10#top=0 From the error it seems that gradle is trying to find the virtualenv command in beam/python folder. I am able to run virtualenv from the bash directly and PATH seems to be setup correctly. Anypointers about what might be happening? org.gradle.api.tasks.TaskExecutionException : Execution failed for task ':beam-sdks-python:setupVirtualenv'. Open stacktrace Caused by: org.gradle.process.internal.ExecException : A problem occurred starting process 'command 'virtualenv'' Open stacktrace Caused by: net.rubygrapefruit.platform.NativeException : Could not start 'virtualenv' Open stacktrace Caused by: java.io.IOException : Cannot run program "virtualenv" (in directory "/tmp/beam/beam/sdks/python"): error=2, No such file or directory Close stacktrace at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start (DefaultProcessLauncher.java:25) at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start (WrapperProcessLauncher.java:36) at org.gradle.process.internal.ExecHandleRunner.run (ExecHandleRunner.java:67) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures .onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run (ManagedExecutorImpl.java:46) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. run(ThreadFactoryImpl.java:55) Caused by: java.io.IOException : error=2, No such file or directory Close stacktrace at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start (DefaultProcessLauncher.java:25) at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start (WrapperProcessLauncher.java:36) at org.gradle.process.internal.ExecHandleRunner.run (ExecHandleRunner.java:67) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable. run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures .onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run (ManagedExecutorImpl.java:46) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable. run(ThreadFactoryImpl.java:55) >>>
