After Coverity upgraded their build system this weekend ( https://twitter.com/CoverityScan/status/751106512097914880) we can finally use Coverity again for static code analyses! a) There are many non-relevant issues right now (but Coverity is able to learn and ignore them for future builds), Benjamin Bannier and I will go through the list, open Jira issues (label: coverity) for the relevant ones and discard the non-relevant ones. Please be patient and wait for us to do so, otherwise, we might be duplicating work. b) Furthermore, we will set up a weekly Coverity build for HEAD (and maybe we should also consider runs for RCs and releases).
Joerg P.S. In order to login into the Coverity project, you need to request access. Feel free to ping me if you experience issues. ---------- Forwarded message ---------- From: <scan-ad...@coverity.com> Date: Mon, Jul 11, 2016 at 3:09 PM Subject: Coverity Scan: Analysis completed for Mesos To: jo...@mesosphere.io Your request for analysis of Mesos has been completed successfully. The results are available at https://scan.coverity.com/projects/mesos Analysis Summary: New defects found: 288 Defects eliminated: 0 If you have difficulty understading any defects, email us at scan-ad...@coverity.com, or post your question to the Coverity Community at https://communities.coverity.com/community/scan-(open-source)/content
