Open sunilheggodu opened 4 years ago
For static analysis, we already have cppcheck and clang running for glusterfs.
Both are good but for different use cases. Specifically, ASAN and TSAN are not for static analysis, but runtime.
Today I spent some time figuring out the issue with ASAN build runs that we have in place. It's failing on Centos7 and I have created an issue for it https://github.com/gluster/glusterfs/issues/1426
https://build.gluster.org/job/asan/226/consoleFull has console output for ASAN on Centos8
It looks like it aborted and log files were not collected?
07:30:14.388 ================================================================================
07:30:14.411 [16:29:10] Running tests in file ./tests/basic/fencing/fencing-crash-conistency.t
07:30:16.469 Build timed out (after 450 minutes). Marking the build as aborted.
07:30:16.543 Build was aborted
07:30:16.554 Performing Post build task...
07:30:16.556 Match found for :Build was aborted : True
Yes, it was aborted because it took more than 450 mins for this build. I would give a try with increased timeout though more than 7hours might be imperssible.
We should probably collect logs also for aborted builds. Not sure how easy it is.
So ASAN is blocked on https://github.com/gluster/glusterfs/issues/3010 and a patch was posted.
Please enable the below jenkin jobs for gluster with frequency of a week.
https://build.gluster.org/job/asan/
https://build.gluster.org/job/tsan/