[Qa-jenkins-scm] Build failed in Jenkins: reproducible_setup_fdroid_build_environment_profitbricks3 #28

jenkins at jenkins.debian.net jenkins at jenkins.debian.net
Thu Feb 11 15:52:15 UTC 2016


See <https://jenkins.debian.net/job/reproducible_setup_fdroid_build_environment_profitbricks3/28/>

------------------------------------------
[...truncated 163 lines...]
+ mkdir /var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/VirtualBox
+ VBoxManage setproperty machinefolder /var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/virtualbox.d
+ VBoxManage setproperty logginglevel debug
+ export VAGRANT_HOME=/var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/vagrant.d
+ VAGRANT_HOME=/var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/vagrant.d
+ mkdir /var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/vagrant.d
+ cd /var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver
+ echo 'debian_mirror = '\''http://ftp.uk.debian.org/debian/'\'''
+ echo 'boot_timeout = 1200'
+ echo 'apt_package_cache = True'
+ ./makebuildserver
...shasum verified for android-sdk_r24.4.1-linux.tgz
...shasum verified for android-platform-3.zip
...shasum verified for android-platform-4.zip
...shasum verified for android-platform-5.zip
...shasum verified for android-platform-6.zip
...shasum verified for android-platform-7.zip
...shasum verified for android-platform-8.zip
...shasum verified for android-platform-9.zip
...shasum verified for android-platform-10.zip
...shasum verified for android-platform-11.zip
...shasum verified for android-platform-12.zip
...shasum verified for android-platform-13.zip
...shasum verified for android-platform-14.zip
...shasum verified for android-platform-15.zip
...shasum verified for android-platform-16.zip
...shasum verified for android-platform-17.zip
...shasum verified for android-platform-18.zip
...shasum verified for android-platform-19.zip
...shasum verified for android-platform-20.zip
...shasum verified for android-platform-21.zip
...shasum verified for android-platform-22.zip
...shasum verified for android-platform-23.zip
...shasum verified for build-tools-17.0.0.zip
...shasum verified for build-tools-18.0.1.zip
...shasum verified for build-tools-18.1.0.zip
...shasum verified for build-tools-18.1.1.zip
...shasum verified for build-tools-19.0.0.zip
...shasum verified for build-tools-19.0.1.zip
...shasum verified for build-tools-19.0.2.zip
...shasum verified for build-tools-19.0.3.zip
...shasum verified for build-tools-19.1.0.zip
...shasum verified for build-tools-20.0.0.zip
...shasum verified for build-tools-21.0.0.zip
...shasum verified for build-tools-21.0.1.zip
...shasum verified for build-tools-21.0.2.zip
...shasum verified for build-tools-21.1.0.zip
...shasum verified for build-tools-21.1.1.zip
...shasum verified for build-tools-21.1.2.zip
...shasum verified for build-tools-22.0.0.zip
...shasum verified for build-tools-22.0.1.zip
...shasum verified for build-tools-23.0.0.zip
...shasum verified for build-tools-23.0.1.zip
...shasum verified for build-tools-23.0.2.zip
...shasum verified for gradle-1.4-bin.zip
...shasum verified for gradle-1.6-bin.zip
...shasum verified for gradle-1.7-bin.zip
...shasum verified for gradle-1.8-bin.zip
...shasum verified for gradle-1.9-bin.zip
...shasum verified for gradle-1.10-bin.zip
...shasum verified for gradle-1.11-bin.zip
...shasum verified for gradle-1.12-bin.zip
...shasum verified for gradle-2.1-bin.zip
...shasum verified for gradle-2.2.1-bin.zip
...shasum verified for gradle-2.3-bin.zip
...shasum verified for gradle-2.4-bin.zip
...shasum verified for gradle-2.5-bin.zip
...shasum verified for gradle-2.6-bin.zip
...shasum verified for gradle-2.7-bin.zip
...shasum verified for gradle-2.8-bin.zip
...shasum verified for gradle-2.9-bin.zip
...shasum verified for gradle-2.10-bin.zip
...shasum verified for Kivy-1.7.2.tar.gz
...shasum verified for android-ndk-r10e-linux-x86.bin
...shasum verified for android-ndk-r9b-linux-x86.tar.bz2
...shasum verified for android-ndk-r9b-linux-x86-legacy-toolchains.tar.bz2
No existing server - building from scratch
Configuring build server VM
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'jessie32' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'jessie32' (v0) for provider: virtualbox
    default: Downloading: file:///var/lib/jenkins/.cache/fdroidserver/jessie32.box

    default: Progress: 0% (Rate: 0/s, Estimated time remaining: --:--:--)
    default: Progress: 14% (Rate: 383M/s, Estimated time remaining: 0:00:02)
    default: Progress: 63% (Rate: 550M/s, Estimated time remaining: 0:00:01)
==> default: Successfully added box 'jessie32' (v0) for 'virtualbox'!
==> default: Importing base box 'jessie32'...

Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%
Progress: 50%
Progress: 60%
Progress: 70%
Progress: 80%
Progress: 90%
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: buildserver_default_1455204942129_40068
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
Failed to configure server
+ cleanup_all
++ date -u
Thu Feb 11 15:55:46 UTC 2016 - cleanup in progress...
+ echo 'Thu Feb 11 15:55:46 UTC 2016 - cleanup in progress...'
+ ps auxww
+ grep VBox
jenkins   4114  0.0  0.0  12816  1560 ?        S    15:55   0:00 grep VBox
jenkins  26884  3.1  0.0 114608 10744 ?        S    15:35   0:38 /usr/lib/virtualbox/VBoxXPCOMIPCD
jenkins  26889  7.8  0.1 541104 16760 ?        Sl   15:35   1:37 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
jenkins  27580  2.7  0.6 1409764 108044 ?      Sl   15:35   0:33 /usr/lib/virtualbox/VBoxHeadless --comment buildserver_default_1455204942129_40068 --startvm 6444aaa2-9eed-4c8e-8ecd-b8d3e2321028 --vrde config
+ cd /var/lib/jenkins/userContent/reproducible/fdroid/fdroidserver/buildserver
+ vagrant halt
==> default: Attempting graceful shutdown of VM...
    default: Guest communication could not be established! This is usually because
    default: SSH is not running, the authentication information was changed,
    default: or some other networking issue. Vagrant will force halt, if
    default: capable.
==> default: Forcing shutdown of VM...
+ sleep 5
+ killall VBoxHeadless
VBoxHeadless: no process found
+ true
+ sleep 5
+ killall -9 VBoxHeadless
VBoxHeadless: no process found
+ true
++ date -u
Thu Feb 11 15:57:16 UTC 2016 - cleanup done.
+ echo 'Thu Feb 11 15:57:16 UTC 2016 - cleanup done.'
+ cleanup_all
++ date -u
Thu Feb 11 15:57:16 UTC 2016 - cleanup in progress...
+ echo 'Thu Feb 11 15:57:16 UTC 2016 - cleanup in progress...'
+ killall VBoxHeadless
VBoxHeadless: no process found
+ true
+ sleep 10
++ date -u
Thu Feb 11 15:57:26 UTC 2016 - cleanup done.
+ echo 'Thu Feb 11 15:57:26 UTC 2016 - cleanup done.'
Thu Feb 11 15:57:26 UTC 2016 - /srv/jenkins/bin/reproducible_setup_fdroid_build_environment.sh stopped running as /tmp/jenkins-script-ouvjzcRS, which will now be removed.
Build step 'Execute shell' marked build as failure



More information about the Qa-jenkins-scm mailing list