|
From: Julian S. <js...@ac...> - 2019-04-08 09:11:16
|
Greetings. A first release candidate for 3.15.0 is available at https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 (md5 = 56d9f5e25615d48110da0aa5764d481e) Please give it a try on platforms that are important for you. If no serious issues are reported, the 3.15.0 final release will happen on 12 April, that is, this coming Friday. J |
|
From: Mark W. <ma...@kl...> - 2019-04-09 07:02:34
|
Hi, On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > A first release candidate for 3.15.0 is available at > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > (md5 = 56d9f5e25615d48110da0aa5764d481e) > > Please give it a try on platforms that are important for you. If no serious > issues are reported, the 3.15.0 final release will happen on 12 April, that > is, this coming Friday. For users are binary rpms for fedora and centos in koji and on copr if people find that easier to use for testing: https://koji.fedoraproject.org/koji/buildinfo?buildID=1246875 https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/ For developers the build.logs do contain the make regtest diffs for any failing tests. Cheers, Mark |
|
From: Mark W. <ma...@kl...> - 2019-04-10 12:11:32
|
On Tue, 2019-04-09 at 09:02 +0200, Mark Wielaard wrote: > Hi, > > On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > > A first release candidate for 3.15.0 is available at > > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > > (md5 = 56d9f5e25615d48110da0aa5764d481e) > > > > Please give it a try on platforms that are important for you. If > > no serious > > issues are reported, the 3.15.0 final release will happen on 12 > > April, that > > is, this coming Friday. > > For users are binary rpms for fedora and centos in koji and on copr > if > people find that easier to use for testing: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1246875 > https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/ > > For developers the build.logs do contain the make regtest diffs for > any > failing tests. I did new builds with the one extra commit and a couple of bug fixes: https://koji.fedoraproject.org/koji/buildinfo?buildID=1247329 https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/build/881204/ This includes the following extra fixes: valgrind commit b2d2da64b0de1c4d657b63187967b68606e84711 GET_STARTREGS for s390: fix register constraint KDE#406352 RC1 fails cachegrind/callgrind ann tests because of missing a.c KDE#406360 memcheck/tests/libstdc++.supp needs more supression variants KDE#406354 dhat is broken on x86 (32bit) KDE#406355 mcsignopass and mcsigpass fails due to a difference in gdb output KDE#406357 RC1 fails gdbserver_tests because of gdb output change I hand tested them all (because I made the mistake of only running the nonexp-regtest (which doesn't include gdbserver_tests) and messed up the data on the a.c file, which generates a warning, but shows the fix itself is good. May I push these fixes to git? Should they go on the master branch, or is there a 3.15.0 branch already? Thanks, Mark |
|
From: Mark W. <ma...@kl...> - 2019-04-09 12:08:29
|
On Mon, 2019-04-08 at 10:25 -0700, Carl Love wrote: > I have run RC1 on Power 7, Power 8 LE, Power 8 BE and Power 9 and > noted each system the same four post errors that I did not see last > week when I tested patches to be committed. The errors are: > > cachegrind/tests/ann1 (post) > cachegrind/tests/ann2 (post) > callgrind/tests/ann1 (post) > callgrind/tests/ann2 (post) > > I looked a little into the errors. I am not familiar with the tests. > > The diff files appear to be consistent across systems. It is indeed failing on other systems too. I filed the following bug, with proposed fix: https://bugs.kde.org/show_bug.cgi?id=406352 > I can't say for sure but I am guessing these will be architecture > independent errors. Cheers, Mark |
|
From: Julian S. <js...@ac...> - 2019-04-11 08:56:27
|
Thank you to everybody who tested RC1, sent reports and bug fixes. RC2 is now available at https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC2.tar.bz2 (md5 = 672e065ec63ae127ee4439cd296fb142). It contains fixes for five minor regression test failures, but nothing major. Unless any serious failures are reported in RC2, this is very likely to morph into the final 3.15.0 release. J > On 08/04/2019 11:11, Julian Seward wrote: > > A first release candidate for 3.15.0 is available at > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > (md5 = 56d9f5e25615d48110da0aa5764d481e) > > Please give it a try on platforms that are important for you. If no serious > issues are reported, the 3.15.0 final release will happen on 12 April, that > is, this coming Friday. > > J |