On 2/20/19 8:11 AM, Martin Sebor wrote: > On 2/20/19 7:25 AM, Jeff Law wrote: >> On 2/20/19 5:36 AM, Pedro Alves wrote: >>> On 02/05/2019 05:07 PM, Jeff Law wrote: >>>> FWIW, I've been doing Fedora rawhide builds with gcc-9 since early Jan. >>>> Not everything builds with -Wall -Werror, but lots of packages do. >>>> I've only seen one maybe-uninit warning cause problems -- it was >>>> spurious and for a memory object. I didn't dig into it at all. >>> >>> Do you have insight into how many Fedora packages explicitly disable >>> maybe-uninit? I really don't know the answer to that, but I'd at least >>> keep that in mind as a possible reason for the warning seemingly >>> not causing trouble often. >> Unfortunately not. And my tester only saves failed log files, so I >> can't just grep the log files for it. > > Would it difficult to add a pass over the build logs to scan for > these sorts of things? E.g., count the number of instances of > each warning in builds that don't use -Werror? It's essentially the same as saving the successful logs :-)
Everything is built with fedpkg which buries the log files. For a failed build the scripts dig them out of the filesystem and dump them to stdout. Doing the same for a successful build wouldn't be hard. Once that's in place we can scan for warnings or whatever else, even in a successful build. I'll try to get that added for the next mass test which would start Sunday after the next gcc-9 snapshot. jeff
