[Qa-jenkins-scm] Build failed in Jenkins: reproducible_fdroid_build_apps #1184

jenkins at jenkins.debian.net jenkins at jenkins.debian.net
Mon Aug 23 23:19:48 BST 2021


See <https://jenkins.debian.net/job/reproducible_fdroid_build_apps/1184/display/redirect?page=changes>

Changes:

[root] gradle v7.2

[root] Android NDK None (None)

[hans] Remove waring about no config file

[hans] Update README.md


------------------------------------------
[...truncated 17.52 MB...]
  File "/usr/lib/python3/dist-packages/vagrant/__init__.py", line 962, in _call_vagrant_command
    subprocess.check_call(command, cwd=self.root, stdout=out_fh,
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/vagrant', 'destroy', '--force']' returned non-zero exit status 1.
2021-08-23 22:19:26,821 DEBUG: deleted vagrant dir: /var/lib/jenkins/userContent/reproducible/reproducible_fdroid_build_apps/fdroiddata/builder/.vagrant
2021-08-23 22:19:26,821 DEBUG: vagrant global-status --prune
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:27,547 DEBUG: pruning global vagrant status failed: Command '['vagrant', 'global-status', '--prune']' returned non-zero exit status 1.
2021-08-23 22:19:27,547 INFO: starting buildserver
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:28,877 ERROR: Could not build app akk.astro.droid.moonphase: could not bring up vm 'builder_default'
==== detail begin ====
Command '['/usr/bin/vagrant', 'up', '--provision', '--provider=virtualbox']' returned non-zero exit status 1.
==== detail end ====
2021-08-23 22:19:28,878 DEBUG: Setting 7200 sec timeout for this build
2021-08-23 22:19:28,928 DEBUG: Getting git vcs interface for https://github.com/fossasia/susi_android
2021-08-23 22:19:28,928 DEBUG: > git --version
git version 2.30.2
2021-08-23 22:19:29,136 INFO: Using git version 2.30.2
2021-08-23 22:19:29,137 DEBUG: Checking 1.1.0
2021-08-23 22:19:29,137 INFO: Building version 1.1.0 (16) of ai.susi
2021-08-23 22:19:29,138 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,138 DEBUG: > git rev-parse --show-toplevel
2021-08-23 22:19:29,347 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,347 DEBUG: > git submodule foreach --recursive git reset --hard
2021-08-23 22:19:29,455 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,456 DEBUG: > git reset --hard
2021-08-23 22:19:29,664 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,664 DEBUG: > git submodule foreach --recursive git clean -dffx
2021-08-23 22:19:29,771 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,772 DEBUG: > git clean -dffx
2021-08-23 22:19:29,878 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:29,878 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com fetch origin
2021-08-23 22:19:30,387 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:30,388 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com fetch --prune --tags --force origin
2021-08-23 22:19:30,897 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:30,897 DEBUG: > git remote set-head origin --auto
2021-08-23 22:19:31,708 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:31,708 DEBUG: > git checkout -f v1.1.0
2021-08-23 22:19:31,917 DEBUG: Directory: build/ai.susi
2021-08-23 22:19:31,917 DEBUG: > git clean -dffx
2021-08-23 22:19:32,025 DEBUG: could not confirm that either virtualbox or kvm/libvirt are installed
2021-08-23 22:19:32,654 INFO: 'virtualbox' buildserver box available, using that
2021-08-23 22:19:32,654 DEBUG: vm uuid is None
2021-08-23 22:19:32,655 INFO: destroying buildserver before build
2021-08-23 22:19:32,655 INFO: destroying vm 'builder_default'
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
2021-08-23 22:19:33,322 ERROR: vagrant destroy failed: Command '['/usr/bin/vagrant', 'destroy', '--force']' returned non-zero exit status 1.
Traceback (most recent call last):
  File "/var/lib/jenkins/userContent/reproducible/reproducible_fdroid_build_apps/fdroidserver/vmtools.py", line 271, in destroy
    self.vgrnt.destroy()
  File "/usr/lib/python3/dist-packages/vagrant/__init__.py", line 417, in destroy
    self._call_vagrant_command(['destroy', vm_name, '--force'])
  File "/usr/lib/python3/dist-packages/vagrant/__init__.py", line 962, in _call_vagrant_command
    subprocess.check_call(command, cwd=self.root, stdout=out_fh,
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/vagrant', 'destroy', '--force']' returned non-zero exit status 1.
2021-08-23 22:19:33,324 DEBUG: deleted vagrant dir: /var/lib/jenkins/userContent/reproducible/reproducible_fdroid_build_apps/fdroiddata/builder/.vagrant
2021-08-23 22:19:33,324 DEBUG: vagrant global-status --prune
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:34,050 DEBUG: pruning global vagrant status failed: Command '['vagrant', 'global-status', '--prune']' returned non-zero exit status 1.
2021-08-23 22:19:34,051 INFO: starting buildserver
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:35,383 ERROR: Could not build app ai.susi: could not bring up vm 'builder_default'
==== detail begin ====
Command '['/usr/bin/vagrant', 'up', '--provision', '--provider=virtualbox']' returned non-zero exit status 1.
==== detail end ====
2021-08-23 22:19:35,384 DEBUG: Setting 7200 sec timeout for this build
2021-08-23 22:19:35,434 DEBUG: Getting git vcs interface for https://github.com/anthonycr/Lightning-Browser.git
2021-08-23 22:19:35,434 DEBUG: > git --version
git version 2.30.2
2021-08-23 22:19:35,643 INFO: Using git version 2.30.2
2021-08-23 22:19:35,643 DEBUG: Checking 5.1.0
2021-08-23 22:19:35,644 DEBUG: Setting 7200 sec timeout for this build
2021-08-23 22:19:35,693 DEBUG: Getting git vcs interface for https://git.code.sf.net/p/androidspeedo/code
2021-08-23 22:19:35,693 DEBUG: > git --version
git version 2.30.2
2021-08-23 22:19:35,900 INFO: Using git version 2.30.2
2021-08-23 22:19:35,901 DEBUG: Checking 1.0
2021-08-23 22:19:35,901 DEBUG: Setting 7200 sec timeout for this build
2021-08-23 22:19:35,950 DEBUG: Getting git vcs interface for https://github.com/jdmonin/anstop
2021-08-23 22:19:35,950 DEBUG: > git --version
git version 2.30.2
2021-08-23 22:19:36,159 INFO: Using git version 2.30.2
2021-08-23 22:19:36,159 DEBUG: Checking 1.5
2021-08-23 22:19:36,159 INFO: Building version 1.5 (10) of An.stop
2021-08-23 22:19:36,160 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,160 DEBUG: > git rev-parse --show-toplevel
2021-08-23 22:19:36,368 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,368 DEBUG: > git submodule foreach --recursive git reset --hard
2021-08-23 22:19:36,475 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,476 DEBUG: > git reset --hard
2021-08-23 22:19:36,683 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,683 DEBUG: > git submodule foreach --recursive git clean -dffx
2021-08-23 22:19:36,791 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,792 DEBUG: > git clean -dffx
2021-08-23 22:19:36,899 DEBUG: Directory: build/An.stop
2021-08-23 22:19:36,899 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com fetch origin
2021-08-23 22:19:37,408 DEBUG: Directory: build/An.stop
2021-08-23 22:19:37,408 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com fetch --prune --tags --force origin
2021-08-23 22:19:37,919 DEBUG: Directory: build/An.stop
2021-08-23 22:19:37,920 DEBUG: > git remote set-head origin --auto
2021-08-23 22:19:38,529 DEBUG: Directory: build/An.stop
2021-08-23 22:19:38,530 DEBUG: > git checkout -f v1.5
2021-08-23 22:19:38,739 DEBUG: Directory: build/An.stop
2021-08-23 22:19:38,739 DEBUG: > git clean -dffx
2021-08-23 22:19:38,847 DEBUG: could not confirm that either virtualbox or kvm/libvirt are installed
2021-08-23 22:19:39,479 INFO: 'virtualbox' buildserver box available, using that
2021-08-23 22:19:39,480 DEBUG: vm uuid is None
2021-08-23 22:19:39,480 INFO: destroying buildserver before build
2021-08-23 22:19:39,480 INFO: destroying vm 'builder_default'
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
2021-08-23 22:19:40,149 ERROR: vagrant destroy failed: Command '['/usr/bin/vagrant', 'destroy', '--force']' returned non-zero exit status 1.
Traceback (most recent call last):
  File "/var/lib/jenkins/userContent/reproducible/reproducible_fdroid_build_apps/fdroidserver/vmtools.py", line 271, in destroy
    self.vgrnt.destroy()
  File "/usr/lib/python3/dist-packages/vagrant/__init__.py", line 417, in destroy
    self._call_vagrant_command(['destroy', vm_name, '--force'])
  File "/usr/lib/python3/dist-packages/vagrant/__init__.py", line 962, in _call_vagrant_command
    subprocess.check_call(command, cwd=self.root, stdout=out_fh,
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/vagrant', 'destroy', '--force']' returned non-zero exit status 1.
2021-08-23 22:19:40,150 DEBUG: deleted vagrant dir: /var/lib/jenkins/userContent/reproducible/reproducible_fdroid_build_apps/fdroiddata/builder/.vagrant
2021-08-23 22:19:40,150 DEBUG: vagrant global-status --prune
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:40,877 DEBUG: pruning global vagrant status failed: Command '['vagrant', 'global-status', '--prune']' returned non-zero exit status 1.
2021-08-23 22:19:40,878 INFO: starting buildserver
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
2021-08-23 22:19:42,207 ERROR: Could not build app An.stop: could not bring up vm 'builder_default'
==== detail begin ====
Command '['/usr/bin/vagrant', 'up', '--provision', '--provider=virtualbox']' returned non-zero exit status 1.
==== detail end ====
2021-08-23 22:19:42,208 INFO: Finished
2021-08-23 22:19:42,209 INFO: 2714 builds failed
+ vagrant global-status
id       name    provider   state    directory                                                                                         
---------------------------------------------------------------------------------------------------------------------------------------
26550e4  default virtualbox poweroff /var/lib/jenkins/userContent/reproducible/reproducible_setup_fdroid_build_environment/buildserver 
 
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
+ '[' -d builder ']'
+ cd builder
+ vagrant status
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
+ cleanup_all
+ set +e
++ date -u
Mon 23 Aug 2021 10:19:43 PM UTC - cleanup in progress...
+ echo 'Mon 23 Aug 2021 10:19:43 PM UTC - cleanup in progress...'
+ killall adb
adb: no process found
+ killall gpg-agent
++ date -u
Mon 23 Aug 2021 10:19:43 PM UTC - cleanup done.
Mon 23 Aug 2021 10:19:43 PM UTC - reproducible_fdroid_build_apps.sh stopped running as /tmp/jenkins-script-XyEpFG3s, removing.
+ echo 'Mon 23 Aug 2021 10:19:43 PM UTC - cleanup done.'

SSH EXIT CODE: 1
Build step 'Execute shell' marked build as failure



More information about the Qa-jenkins-scm mailing list