Re: Valgrind-3.20.0.RC1 is available for testing

Carl Love <cel-r/[email protected]> Thu, 20 Oct 2022 13:25:44 -0700
Newsgroups gmane.comp.debugging.valgrind.devel,gmane.comp.debugging.valgrind
Message-ID <[email protected]>
Mark:

On Thu, 2022-10-20 at 01:52 +0200, Mark Wielaard wrote:
> Greetings.
> 
> A first release candidate for 3.20.0 is available at
> https://sourceware.org/pub/valgrind/valgrind-3.20.0.RC1.tar.bz2  
> (md5 = 981b9276536843090700c1268549186e)
> 
> Please give it a try on platforms that are important for you.  If no
> serious issues are reported, the 3.20.0 final release will happen on
> 22 October.

The RC was run on Power 7, Power 8BE, Power 8LE, Power 9 and Power 10. 
The number of failures and stdout failures for the 3.20RC was the same
or lower than what was seen on 3.19 for each of the platforms.

The only issue noted, as discussed on #valgrind-dev channel, is the
addition of four post errors for the 3.20RC tree on all of the Power
platforms.  Specifically:

cachegrind/tests/ann1                    (post)
cachegrind/tests/ann2                    (post)
callgrind/tests/ann1                     (post)
callgrind/tests/ann2                     (post)

The output from  cachegrind/tests/ann1.post.diff is:

--- ann1.post.exp	2021-01-21 09:09:33.000000000 -0600
+++ ann1.post.out	2022-10-20 14:07:33.272141328 -0500
@@ -33,6 +33,13 @@
 --------------------------------------------------------------------
-----------
-
 -- Auto-annotated source: a.c
 --------------------------------------------------------------------
-----------
-
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@
+@@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@
WARNING @@
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@
+@ Source file 'a.c' is more recent than input file 'cgout-test'.
+@ Annotations may not be correct.
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@
+
 Ir        I1mr ILmr 
 
         2    0    0  int main(void) {

As discussed on the #valgrind-dev channel, this appears to be a
timestamp issue.  Doing a touch * in directory cachegrind/tests seems
to fix all four post errors.

No other issues were noted.  I would vote to do the touch * command and
go ahead with the release.

                       Carl 



_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers