Thank you Kaleb. Shall we start somwhere in terms of automation? The cppcheck results look the shortest[1]. If we can commit to fixing all of them in the next 1 month, I can kick off a non-voting smoke job. We'll make it vote after 1 month. I guss the cli and experimental xlator (and a few more xlators, please check log) owners need to confirm that this is something we can target to fix. And commit to keeping fixed. Thoughts? [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-cppcheck/2016-12-19-2bb23136/cppcheck.txt On Mon, Dec 19, 2016 at 11:33:16AM -0500, Kaleb S. KEITHLEY wrote: > Hi, > > Nightly runs of static analyzers have been migrated to a new host > (inside Red Hat) running Fedora 25. (The old host was running F23.) > > With that update comes clang-3.8 (from 3.7) and cppcheck-1.75 (from 1.70). > > Independent of that, coverity was updated from 7.7.0 to 8.6.0. > > As always the results of coverity scan, clang compile, clang analyzer, > and cppcheck are available at > https://download.gluster.org/pub/gluster/glusterfs/static-analysis/ > > Longer term plans still include migrating these nightly tasks to the > "community cage" and better integration with Gerrit and Jenkins. > > -- > > Kaleb -- nigelb
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
