Virtual env setup is failing because of the following error. Can we reboot the machine to see if it fixes the issue?
:beam-sdks-python:setupVirtualenv FAILED Traceback (most recent call last): New python executable in /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Portable_Python_Commit@2 /src/build/gradleenv/1327086738/bin/python2 File "/usr/lib/python3/dist-packages/virtualenv.py", line 2363, in <module> Also creating executable in /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Portable_Python_Commit@2 /src/build/gradleenv/1327086738/bin/python main() File "/usr/lib/python3/dist-packages/virtualenv.py", line 719, in main symlink=options.symlink) File "/usr/lib/python3/dist-packages/virtualenv.py", line 942, in create_environment site_packages=site_packages, clear=clear, symlink=symlink)) File "/usr/lib/python3/dist-packages/virtualenv.py", line 1423, in install_python raise e OSError: [Errno 11] Resource temporarily unavailable Running virtualenv with interpreter /usr/bin/python2 On Mon, Dec 3, 2018 at 1:12 PM Ankur Goenka <[email protected]> wrote: > Hi, > > I see that beam9 is failing significantly more number of python related > builds [1]. > This also results in more failure of beam_PreCommit_Portable_Python_Commit > [2] on beam9. > Can someone with access to beam9 take a look? > > Thanks, > Ankur > > > [1] https://builds.apache.org/computer/beam9/builds > [2] > https://builds.apache.org/job/beam_PreCommit_Portable_Python_Commit/buildTimeTrend >
