Your message dated Mon, 14 Aug 2017 14:50:53 +0000
with message-id <[email protected]>
and subject line Bug#872075: fixed in redis 4:4.0.1-7
has caused the Debian Bug report #872075,
regarding redis FTBFS: test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
872075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872075
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: redis
Version: 4:4.0.1-6
Severity: serious

https://buildd.debian.org/status/package.php?p=redis&suite=sid

...
Cleanup: may take some time... OK
taskset --cpu-list 0 ./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
05:27:25> (init) Restart killed instances: OK
05:27:25> (init) Remove old master entry from sentinels: OK
05:27:25> (init) Create a master-slaves cluster of 5 instances: OK
05:27:26> (init) Sentinels can start monitoring a master: OK
05:27:26> (init) Sentinels can talk with the master: OK
05:27:26> (init) Sentinels are able to auto-discover other sentinels: OK
05:27:28> (init) Sentinels are able to auto-discover slaves: OK
05:27:28> Basic failover works if the master is down: OK
05:27:31> New master 127.0.0.1:30002 role matches: OK
05:27:31> All the other slaves now point to the new master: OK
05:27:31> The old master eventually gets reconfigured as a slave: OK
05:27:42> ODOWN is not possible without N (quorum) Sentinels reports: OK
05:27:42> Failover is not possible without majority agreement: OK
05:27:43> Failover works if we configure for absolute agreement: OK
05:27:47> New master 127.0.0.1:30000 role matches: OK
Testing unit: 01-conf-update.tcl
05:27:47> (init) Restart killed instances: OK
05:27:47> (init) Remove old master entry from sentinels: OK
05:27:47> (init) Create a master-slaves cluster of 5 instances: OK
05:27:48> (init) Sentinels can start monitoring a master: OK
05:27:48> (init) Sentinels can talk with the master: OK
05:27:48> (init) Sentinels are able to auto-discover other sentinels: OK
05:27:50> (init) Sentinels are able to auto-discover slaves: OK
05:27:50> After Sentinel 1 is restarted, its config gets updated: OK
05:27:50> New master 127.0.0.1:30000 role matches: OK
Testing unit: 02-slaves-reconf.tcl
05:27:50> (init) Restart killed instances: OK
05:27:50> (init) Remove old master entry from sentinels: OK
05:27:50> (init) Create a master-slaves cluster of 5 instances: OK
05:27:50> (init) Sentinels can start monitoring a master: OK
05:27:50> (init) Sentinels can talk with the master: OK
05:27:50> (init) Sentinels are able to auto-discover other sentinels: OK
05:27:52> (init) Sentinels are able to auto-discover slaves: OK
05:27:52> Check that slaves replicate from current master: OK
05:27:52> Crash the master and force a failover: OK
05:27:56> Check that slaves replicate from current master: OK
05:28:06> Kill a slave instance: OK
05:28:06> Crash the master and force a failover: OK
05:28:09> Check that slaves replicate from current master: OK
05:28:19> Wait for failover to end: OK
05:28:19> Restart killed slave and test replication of slaves again...: OK
05:28:19> 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
05:28:40> (init) Restart killed instances: OK
05:28:40> (init) Remove old master entry from sentinels: OK
05:28:40> (init) Create a master-slaves cluster of 5 instances: OK
05:28:41> (init) Sentinels can start monitoring a master: OK
05:28:41> (init) Sentinels can talk with the master: OK
05:28:41> (init) Sentinels are able to auto-discover other sentinels: OK
05:28:43> (init) Sentinels are able to auto-discover slaves: OK
05:28:43> Manual failover works: OK
05:28:45> New master 127.0.0.1:30004 role matches: OK
05:28:45> All the other slaves now point to the new master: OK
05:28:45> The old master eventually gets reconfigured as a slave: OK
Testing unit: 06-ckquorum.tcl
05:28:55> (init) Restart killed instances: OK
05:28:55> (init) Remove old master entry from sentinels: OK
05:28:55> (init) Create a master-slaves cluster of 5 instances: OK
05:28:55> (init) Sentinels can start monitoring a master: OK
05:28:55> (init) Sentinels can talk with the master: OK
05:28:55> (init) Sentinels are able to auto-discover other sentinels: OK
05:28:57> (init) Sentinels are able to auto-discover slaves: OK
05:28:57> CKQUORUM reports OK and the right amount of Sentinels: OK
05:28:57> CKQUORUM detects quorum cannot be reached: OK
05:28:57> CKQUORUM detects failover authorization cannot be reached: kill: 
(26442): No such process
    while executing
"exec kill -9 $pid"
    (procedure "kill_instance" line 9)
    invoked from within
"kill_instance sentinel 1"
    ("uplevel" body line 4)
    invoked from within
"uplevel 1 $code"
    (procedure "test" line 6)
    invoked from within
"test "CKQUORUM detects failover authorization cannot be reached" {
    set orig_quorum [expr {$num_sentinels/2+1}]
    S 0 SENTINEL SET mymaster quoru..."
    (file "../tests/06-ckquorum.tcl" line 20)
    invoked from within
"source $test"
    (procedure "run_tests" line 9)
    invoked from within
"run_tests"
    (procedure "main" line 5)
    invoked from within
"main"
Cleaning up...
debian/rules:30: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 4:4.0.1-7

We believe that the bug you reported is fixed in the latest version of
redis, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <[email protected]> (supplier of updated redis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 14 Aug 2017 07:35:38 -0700
Source: redis
Binary: redis-server redis-tools redis-sentinel
Built-For-Profiles: nocheck
Architecture: source amd64
Version: 4:4.0.1-7
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb <[email protected]>
Changed-By: Chris Lamb <[email protected]>
Description:
 redis-sentinel - Persistent key-value database with network interface 
(monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 872075
Changes:
 redis (4:4.0.1-7) unstable; urgency=medium
 .
   * Don't let sentinel tests fail the build; they use too many timers to be
     useful and/or meaningful. (Closes: #872075)
Checksums-Sha1:
 c9bc1efb58d49d31f6e2d7da159e88654f94e380 2031 redis_4.0.1-7.dsc
 08996b09636585f14837721bc176439b5f6c993a 36692 redis_4.0.1-7.debian.tar.xz
 55f235a93297245999aae50a63f129310fdd7fac 55414 redis-sentinel_4.0.1-7_amd64.deb
 d57e850bd1294818d248053272a843a5db2fc27e 78540 redis-server_4.0.1-7_amd64.deb
 0f110a809b3987723f2b326bdbecb252303f5940 1418774 
redis-tools-dbgsym_4.0.1-7_amd64.deb
 16470650bdcf2955ac2fe50caf34ff5023839a87 552838 redis-tools_4.0.1-7_amd64.deb
 9747f2da791a91c25a90c6ede325dfef31ff4dce 6015 redis_4.0.1-7_amd64.buildinfo
Checksums-Sha256:
 79f8b5bfa7c41a59c12adbcd69ac0b00b7102f7202d2e4cc1ce642a33efbf5dc 2031 
redis_4.0.1-7.dsc
 638bf76427b714497f519b36717c263ba93a89e31808490be15ecf940759ef84 36692 
redis_4.0.1-7.debian.tar.xz
 f4c502f25449fbe8ed578a0acb36b65e14f713951332a02b2116f2e7b6653dd9 55414 
redis-sentinel_4.0.1-7_amd64.deb
 d31c7b45a4afd9aee61e657100d7cd507b6d872af5456d86a92ecef4e311e816 78540 
redis-server_4.0.1-7_amd64.deb
 8cd9dcd89ebdac3d755ae7eb40a5549bcc985be4546131c1a8d1908a81dfedcc 1418774 
redis-tools-dbgsym_4.0.1-7_amd64.deb
 53ce0c2a94fae8f4944aa832d0ad91b3d46026716c3947c895e847f5f7741209 552838 
redis-tools_4.0.1-7_amd64.deb
 3888f57c9e56054df5dcaf5c3a129c60ebc42014939f1252d344bc0ff96abfab 6015 
redis_4.0.1-7_amd64.buildinfo
Files:
 1bdd93d7536a8f8003482f4463f76662 2031 database optional redis_4.0.1-7.dsc
 1f01bd1a2450f482ede227efa808537d 36692 database optional 
redis_4.0.1-7.debian.tar.xz
 bee5962d93fd7c79ad928b909005fe9f 55414 database optional 
redis-sentinel_4.0.1-7_amd64.deb
 4951f554722ab02e02237b7ae93c28ad 78540 database optional 
redis-server_4.0.1-7_amd64.deb
 36c6327601f379fdeb380d6f83a25eed 1418774 debug extra 
redis-tools-dbgsym_4.0.1-7_amd64.deb
 5b27428d817a53c3e32ea9df1f29082b 552838 database optional 
redis-tools_4.0.1-7_amd64.deb
 dc154eedc6ecb1ce69c5c75312ec578f 6015 database optional 
redis_4.0.1-7_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlmRtWwACgkQHpU+J9Qx
Hli08hAAjvhtTknBZ/C4lXY/DuRXvkJhkEqVCnGyLuVv8yggbwltPqwSPOfgOTpf
xq00r3ecWtuW3CiIVLdHvyjvSoLRvtgbQzTpkr25GJOGGf0M0MhtK9XoP7aQYuir
XVnMtt6JuiRxbT4CDAM+CZuOfbA4IKcA/L7DOlZ6xnbDDEHyWpCbbOEyJ08buaFX
oh5eeo0COhPBXghiOtJ1kDWWkxZzQBfFStVqFpIO5huWUVqIQOL7EBvQ8KmO8+Pn
y+tsOIDoKxJf5QORcHr+ZPNie3STI59rPEV2o3uLNZQ8cgJGzdOzRVdr359GS2AC
kb77lxbJV83yIA4Rne1fY0e6Rpnjar60ilHzJKb1vKuzjckmAFeSGg4nVBx46C5D
y+XQfQy6P9JBvmDHVUccA/QoFjYWn1pBVHrQB8Wh/z9ITNFYhnzufmzcknnyekBQ
Kc4Yo8PthFF5/T23j2dwowDxyekmGZ3C6kiG6LawgWT8IJgq3ORIjoifc07ar9EG
vdNvLcORC2GC75TdnmjctO7BtPUz+o/G1rsJrFd6rAsePvW9CbVcwMflBhdV9GQQ
PCJSnRM692wBhvdQfVsREmz5Q9Wj/vqGGb6lUX9Z2rjQ6pSBzSn/4eEbOMnuEyg1
MddceJxI9Qahj9QH6R92svGFPk1A/MKjRbaNa2+RvzCoMy0Z8eI=
=H6FZ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to