Test execution works again now.

lintPy27 needs to be fixed though. I see the Pr is already out: https://github.com/apache/beam/pull/7249

On 11.12.18 01:01, Yifan Zou wrote:
The ssh key is also missing on the beam9. I've add it back.

On Mon, Dec 10, 2018 at 3:52 PM Yifan Zou <[email protected] <mailto:[email protected]>> wrote:

    The beam9 is set to a premium IP, rebooting...

    On Mon, Dec 10, 2018 at 2:52 PM Yifan Zou <[email protected]
    <mailto:[email protected]>> wrote:

        I am seeing the beam9 was rebooted today at 9:49 am. The external IP was
        reset to a ephemeral IP. I am trying to set it to be the correct
        beam-jenkins IP.

        -Yifan

        On Mon, Dec 10, 2018 at 2:42 PM Valentyn Tymofieiev <[email protected]
        <mailto:[email protected]>> wrote:

            We can file INFRA tickets for requests to reboot machines. Sample:
            https://issues.apache.org/jira/browse/INFRA-16926

            On Mon, Dec 10, 2018 at 2:38 PM Alan Myrvold <[email protected]
            <mailto:[email protected]>> wrote:

                Is someone rebooting it? it appears offline

                https://builds.apache.org/computer/beam9/

                On Mon, Dec 10, 2018 at 1:34 AM Robert Bradshaw
                <[email protected] <mailto:[email protected]>> wrote:

                    The same error is impacting our postcommit tests. Who has
                    permissions to reboot these machines?

                    On Sat, Dec 8, 2018 at 3:13 AM Ankur Goenka
                    <[email protected] <mailto:[email protected]>> wrote:

                        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:setupVirtualenvFAILED
                        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] <mailto:[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

Reply via email to