[Qa-jenkins-scm] Build failed in Jenkins: reproducible_fdroid_test #471

jenkins at jenkins.debian.net jenkins at jenkins.debian.net
Fri Aug 6 05:24:20 BST 2021


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

Changes:

[flx] fix copy_triple_t_store_metadata()

[flx] update test_insert_triple_t_multiple_metadata() test data

[flx] copy_triple_t_store_metadata(): also look in $subdir/*/src/*/play

[flx] add test_insert_triple_t_anysoftkeyboard()

[hans] metadata: remove unused fields and types

[hans] update: AllowedAPKSigningKeys metadata to enforce APK signers

[hans] update: modernize options handling in tests

[hans] Don't fail fdroid update on empty repository


------------------------------------------
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
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_test/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_test/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 c4d3e075cb859c8ce4f0125cd0677a7c53decde7 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c4d3e075cb859c8ce4f0125cd0677a7c53decde7 # timeout=10
Commit message: "Merge branch 'fix_update' into 'master'"
 > git rev-list --no-walk 884870e74eedf3cf69b99e3192fe77056eee0fe3 # timeout=10
[reproducible_fdroid_test] $ /bin/sh -xe /tmp/jenkins3498106929552335504.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh
ssh: connect to host osuosl168-amd64.debian.net port 45047: Connection timed out
Fri  6 Aug 04:23:20 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