[Qa-jenkins-scm] Build failed in Jenkins: reproducible_builder_amd64_12 #60086
jenkins at jenkins.debian.net
jenkins at jenkins.debian.net
Thu Dec 1 17:40:00 UTC 2016
https://jenkins.debian.net/job/reproducible_builder_amd64_12/60086/------------------------------------------
[...truncated 3719 lines...]
[ok]: AOF rewrite of hash with ziplist encoding, string data
[ok]: AOF rewrite of hash with hashtable encoding, string data
[ok]: Client output buffer hard limit is enforced
[ok]: AOF rewrite of hash with ziplist encoding, int data
[ok]: AOF rewrite of hash with hashtable encoding, int data
[ok]: AOF rewrite of zset with ziplist encoding, string data
[ok]: Connect multiple slaves at the same time (issue #141), diskless=no
[ok]: AOF rewrite of zset with skiplist encoding, string data
[ok]: AOF rewrite of zset with ziplist encoding, int data
[ok]: AOF rewrite of zset with skiplist encoding, int data
[ok]: BGREWRITEAOF is delayed if BGSAVE is in progress
[ok]: BGREWRITEAOF is refused if already in progress
[37/40 done]: unit/aofrw (42 seconds)
[ok]: Client output buffer soft limit is not enforced if time is not overreached
[ok]: Stress tester for #3343-alike bugs
[ok]: Client output buffer soft limit is enforced if time is overreached
[38/40 done]: unit/obuf-limits (69 seconds)
[ok]: ziplist implementation: value encoding and backlink
[ok]: ziplist implementation: encoding stress testing
[39/40 done]: unit/type/list-3 (95 seconds)
[ok]: Connect multiple slaves at the same time (issue #141), diskless=yes
[40/40 done]: integration/replication (115 seconds)
The End
Execution time of different units:
0 seconds - unit/printver
0 seconds - unit/type/incr
0 seconds - unit/auth
1 seconds - unit/scan
1 seconds - unit/quit
1 seconds - unit/protocol
1 seconds - unit/keyspace
2 seconds - unit/multi
7 seconds - unit/type/hash
9 seconds - unit/type/set
9 seconds - unit/type/zset
10 seconds - unit/other
3 seconds - integration/aof
1 seconds - integration/rdb
10 seconds - unit/sort
1 seconds - integration/convert-zipmap-hash-on-load
10 seconds - unit/expire
1 seconds - unit/introspection
1 seconds - unit/pubsub
1 seconds - unit/slowlog
11 seconds - unit/type/string
1 seconds - unit/limits
13 seconds - unit/type/list
3 seconds - unit/bitops
5 seconds - unit/maxmemory
7 seconds - unit/introspection-2
7 seconds - unit/scripting
7 seconds - unit/bitfield
18 seconds - integration/replication-2
6 seconds - unit/memefficiency
21 seconds - unit/type/list-2
14 seconds - unit/geo
29 seconds - unit/dump
17 seconds - unit/hyperloglog
32 seconds - integration/replication-3
32 seconds - integration/replication-4
42 seconds - unit/aofrw
69 seconds - unit/obuf-limits
95 seconds - unit/type/list-3
115 seconds - integration/replication
\o/ All tests passed without errors!
Cleanup: may take some time... OK
./runtest-sentinel
Starting sentinel #0 at port 20000
Starting sentinel #1 at port 20001
Starting sentinel #2 at port 20002
Starting sentinel #3 at port 20003
Starting sentinel #4 at port 20004
Starting redis #0 at port 30000
Starting redis #1 at port 30001
Starting redis #2 at port 30002
Starting redis #3 at port 30003
Starting redis #4 at port 30004
Testing unit: 00-base.tcl
11:58:05> (init) Restart killed instances: OK
11:58:05> (init) Remove old master entry from sentinels: OK
11:58:05> (init) Create a master-slaves cluster of 5 instances: OK
11:58:06> (init) Sentinels can start monitoring a master: OK
11:58:06> (init) Sentinels can talk with the master: OK
11:58:06> (init) Sentinels are able to auto-discover other sentinels: OK
11:58:08> (init) Sentinels are able to auto-discover slaves: OK
11:58:08> Basic failover works if the master is down: OK
11:58:11> New master 127.0.0.1:30004 role matches: OK
11:58:11> All the other slaves now point to the new master: OK
11:58:11> The old master eventually gets reconfigured as a slave: OK
11:58:21> ODOWN is not possible without N (quorum) Sentinels reports: OK
11:58:23> Failover is not possible without majority agreement: OK
11:58:25> Failover works if we configure for absolute agreement: OK
11:58:29> New master 127.0.0.1:30003 role matches: OK
Testing unit: 01-conf-update.tcl
11:58:29> (init) Restart killed instances: OK
11:58:29> (init) Remove old master entry from sentinels: OK
11:58:29> (init) Create a master-slaves cluster of 5 instances: OK
11:58:30> (init) Sentinels can start monitoring a master: OK
11:58:30> (init) Sentinels can talk with the master: OK
11:58:30> (init) Sentinels are able to auto-discover other sentinels: OK
11:58:32> (init) Sentinels are able to auto-discover slaves: OK
11:58:32> We can failover with Sentinel 1 crashed: OK
11:58:36> After Sentinel 1 is restarted, its config gets updated: OK
11:58:37> New master 127.0.0.1:30003 role matches: OK
Testing unit: 02-slaves-reconf.tcl
11:58:37> (init) Restart killed instances: OK
11:58:37> (init) Remove old master entry from sentinels: OK
11:58:37> (init) Create a master-slaves cluster of 5 instances: OK
11:58:38> (init) Sentinels can start monitoring a master: OK
11:58:38> (init) Sentinels can talk with the master: OK
11:58:38> (init) Sentinels are able to auto-discover other sentinels: OK
11:58:40> (init) Sentinels are able to auto-discover slaves: OK
11:58:40> Check that slaves replicate from current master: OK
11:58:40> Crash the master and force a failover: OK
11:58:43> Check that slaves replicate from current master: OK
11:58:44> Kill a slave instance: OK
11:58:45> Crash the master and force a failover: OK
11:58:49> Check that slaves replicate from current master: OK
11:58:59> Wait for failover to end: OK
11:58:59> Restart killed slave and test replication of slaves again...: OK
11:58:59> Check that slaves replicate from current master: OK
Testing unit: 03-runtime-reconf.tcl
Testing unit: 04-slave-selection.tcl
Testing unit: 05-manual.tcl
11:59:20> (init) Restart killed instances: OK
11:59:20> (init) Remove old master entry from sentinels: OK
11:59:20> (init) Create a master-slaves cluster of 5 instances: OK
11:59:21> (init) Sentinels can start monitoring a master: OK
11:59:21> (init) Sentinels can talk with the master: OK
11:59:21> (init) Sentinels are able to auto-discover other sentinels: OK
11:59:23> (init) Sentinels are able to auto-discover slaves: OK
11:59:23> Manual failover works: OK
11:59:24> New master 127.0.0.1:30001 role matches: OK
11:59:24> All the other slaves now point to the new master: OK
11:59:24> The old master eventually gets reconfigured as a slave: OK
Testing unit: 06-ckquorum.tcl
11:59:34> (init) Restart killed instances: OK
11:59:34> (init) Remove old master entry from sentinels: OK
11:59:34> (init) Create a master-slaves cluster of 5 instances: OK
11:59:35> (init) Sentinels can start monitoring a master: OK
11:59:35> (init) Sentinels can talk with the master: OK
11:59:35> (init) Sentinels are able to auto-discover other sentinels: OK
11:59:37> (init) Sentinels are able to auto-discover slaves: OK
11:59:37> CKQUORUM reports OK and the right amount of Sentinels: OK
11:59:37> CKQUORUM detects quorum cannot be reached: OK
11:59:37> CKQUORUM detects failover authorization cannot be reached: OK
Testing unit: 07-down-conditions.tcl
11:59:44> (init) Restart killed instances: OK
11:59:44> (init) Remove old master entry from sentinels: OK
11:59:44> (init) Create a master-slaves cluster of 5 instances: OK
11:59:44> (init) Sentinels can start monitoring a master: OK
11:59:44> (init) Sentinels can talk with the master: OK
11:59:44> (init) Sentinels are able to auto-discover other sentinels: OK
11:59:46> (init) Sentinels are able to auto-discover slaves: OK
11:59:46> Crash the majority of Sentinels to prevent failovers for this unit: OK
11:59:47> SDOWN is triggered by non-responding but not crashed instance: OK
11:59:57> SDOWN is triggered by crashed instance: OK
12:00:01> SDOWN is triggered by masters advertising as slaves: OK
12:00:38> SDOWN is triggered by misconfigured instance repling with errors: OK
Cleaning up...
GOOD! No errors.
make[1]: Leaving directory '/build/1st/redis-3.2.5'
fakeroot debian/rules binary
dh binary --with systemd
dh_testroot
dh_prep
debian/rules override_dh_auto_install
make[1]: Entering directory '/build/1st/redis-3.2.5'
debian/bin/generate-parts
make[1]: Leaving directory '/build/1st/redis-3.2.5'
dh_install
dh_installdocs
dh_installchangelogs
dh_installexamples
dh_installman
dh_systemd_enable
dh_installinit
dh_systemd_start
dh_installlogrotate
dh_perl
dh_link
dh_strip_nondeterminism
debian/rules override_dh_compress
make[1]: Entering directory '/build/1st/redis-3.2.5'
dh_compress -Xredis-trib.rb
make[1]: Leaving directory '/build/1st/redis-3.2.5'
dh_fixperms
dh_strip
dh_makeshlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-gencontrol: warning: Depends field of package redis-sentinel: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dh_md5sums
dh_builddeb
dpkg-deb: building package 'redis-server-dbgsym' in '../redis-server-dbgsym_3.2.5-4_amd64.deb'.
dpkg-deb: building package 'redis-tools-dbgsym' in '../redis-tools-dbgsym_3.2.5-4_amd64.deb'.
dpkg-deb: building package 'redis-sentinel' in '../redis-sentinel_3.2.5-4_amd64.deb'.
dpkg-deb: building package 'redis-server' in '../redis-server_3.2.5-4_amd64.deb'.
dpkg-deb: building package 'redis-tools' in '../redis-tools_3.2.5-4_amd64.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-genchanges --build=binary >../redis_3.2.5-4_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build redis-3.2.5
dpkg-source: info: using options from redis-3.2.5/debian/source/options: --extend-diff-ignore=^\.travis\.yml$
dpkg-buildpackage: info: binary-only upload (no source included)
I: copying local configuration
I: unmounting /dev/shm filesystem
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env
I: removing directory /srv/workspace/pbuilder/63151 and its subdirectories
I: Current time: Wed Jan 3 12:00:57 -12 2018
I: pbuilder-time-stamp: 1515024057
ls: cannot access b1/*dsc: No such file or directory
Thu Dec 1 17:37:59 UTC 2016 E: Version mismatch between main node (redis_3.2.5-6_amd64.dsc expected) and first build node () for unstable/amd64, aborting. Please upgrade the schroots...
Error: database is locked
/srv/reproducible-results/rbuild-debian-E2pfJqGg/tmp.Nqpi3DVQB7: 80.9% -- replaced with /srv/reproducible-results/rbuild-debian-E2pfJqGg/tmp.Nqpi3DVQB7.gz
INFO: Starting at 2016-12-01 17:38:59.661230
CRITICAL: SQLite database locked, could not execute query:
CRITICAL: "SELECT r.status, r.version, r.build_date
CRITICAL: FROM results AS r JOIN sources AS s
CRITICAL: ON r.package_id=s.id WHERE s.name='redis'
CRITICAL: AND s.architecture='amd64' AND s.suite='testing'"
CRITICAL: Exiting script.
INFO: Finished at 2016-12-01 17:39:59.932576, took: 0:01:00.271374
Warning: cannot update html pages for redis
Thu 1 Dec 17:40:00 UTC 2016 - /srv/jenkins/bin/reproducible_build.sh stopped running as /tmp/jenkins-script-BRD8u6cN, which will now be removed.
Build step 'Execute shell' marked build as failure
More information about the Qa-jenkins-scm
mailing list