[Qa-jenkins-scm] Build failed in Jenkins: reproducible_fdroid_build_apps #1165
jenkins at jenkins.debian.net
jenkins at jenkins.debian.net
Fri Jun 25 10:37:56 BST 2021
See <https://jenkins.debian.net/job/reproducible_fdroid_build_apps/1165/display/redirect?page=changes>
Changes:
[hans] gitlab-ci: switch ubuntu_lts_ppa job to keyserver.ubuntu.com
[hans] gradle-release-checksums.py: check for GitLab token before committing
[hans] this codebase has started to use things introduced in Python 3.5
[64bit+git] rewrite docstrings to match numpy style guide
[64bit+git] rewrite docstrings to match numpy style guide
[64bit+git] Fix pep8 whitespace errors
[64bit+git] apply numpy docstyle
[64bit+git] rewrite docstrings to match numpy style guide
[64bit+git] Fix errors from merge and review
[hans] add require_signature param to scan_apk
[hans] merge scan_apk doc string updates
------------------------------------------
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on osuosl168-amd64.debian.net (osuosl168 amd64) in workspace <https://jenkins.debian.net/job/reproducible_fdroid_build_apps/ws/>
The recommended git tool is: NONE
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://gitlab.com/fdroid/fdroidserver.git
> git init <https://jenkins.debian.net/job/reproducible_fdroid_build_apps/ws/> # timeout=10
Fetching upstream changes from https://gitlab.com/fdroid/fdroidserver.git
> git --version # timeout=10
> git --version # 'git version 2.20.1'
> git fetch --tags --force --progress -- https://gitlab.com/fdroid/fdroidserver.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://gitlab.com/fdroid/fdroidserver.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 3e7ce8ce31890239ae99a94db51fb456264a62d5 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3e7ce8ce31890239ae99a94db51fb456264a62d5 # timeout=10
Commit message: "merge scan_apk doc string updates"
> git rev-list --no-walk ecadad63f1f724941d64ef5eca96fb0f9e4c9904 # timeout=10
[reproducible_fdroid_build_apps] $ /bin/sh -xe /tmp/jenkins3269811126724863184.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh
ssh: connect to host osuosl168-amd64.debian.net port 45047: No route to host
Fri 25 Jun 09:36:55 UTC 2021 - osuosl168-amd64.debian.net seems to be down, sleeping 1min before exiting with error.
Build step 'Execute shell' marked build as failure
More information about the Qa-jenkins-scm
mailing list