On Sun, 2019-01-13 at 13:21 +0000, Luca Boccassi wrote: > On Sun, 2019-01-13 at 14:16 +0100, László Böszörményi (GCS) wrote: > > On Sun, Jan 13, 2019 at 1:27 AM Luca Boccassi <bl...@debian.org> > > wrote: > > > On Sat, 12 Jan 2019, 19:53 László Böszörményi (GCS) <gcs@debian.o > > > rg > > > wrote: > > > > No problem. But I ask for a help with 4.3.1 as one of its > > > > tests > > > > fail > > > > on ppc64el architecture [1]. > > > > The minimal log I see: > > > > "FAIL: tests/test_hwm_pubsub > > > > =========================== > > > > > > > > Assertion failed: check () (src/msg.cpp:347) > > > > FAIL tests/test_hwm_pubsub (exit status: 134)" > > > > > > I've seen that test fail sometimes on the very very slow windows > > > CI > > > we use upstream, I've never reproduced it locally or on porter > > > machines or on the PPC Linux CI we use upstream. > > > I'd suggest to just try to ask wanna-build for a give back, and > > > it > > > will most likely pass. If it still fails I'll hop on a porter box > > > tomorrow. > > > > Tested on plummer and about half the time this test is failed. > > Once > > from ten times an other test is failed as well. I chose to upload > > my > > build instead of a give back as that may fail as well. > > I might have an idea on how to make it more reliable, I'm testing on > kyoto right now, as I've seen there's definitely an issue with > another > test helper doing unaligned pointer access which triggers a sigbus on > sparc64 (it's not a problem in the library thankfully, just in the > unit > test itself).
I'm seeing very strange behaviour on plummer, with a message which internal metadata is getting overwritten. Didn't see that on sparc64 or on my machines, very weird. I'm still looking. In the meanwhile, I've found and fixed the issue with the other 3 tests that seemingly randomly fail - it's not random at all, it's just that they were left with hard-coded IPC file paths, so collisions might happen. I've fixed them to use random paths like the others (those were test_use_fd, test_reconnect_ivl, test_rebind_ipc and test_pair_ipc). Also in the meanwhile, this issue has been assigned CVE-2019-6250, so I'm CC'ing the Debian Security team, as they might want to create a DSA. Dear Security Team, as noted in this ticket this issue affects Stretch and Buster (src:zeromq3 from 4.2.0 to 4.3.0). -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
