Bug 1542163 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Jonathan thank you for the feedback, right now we are relying solely on what Coverity server is providing us, and it seems it fails from time to time. There are several issues why this might happen:
-- The codebase that the patch is used is newer than the last snapshot captured by the coverity server and hence it doesn't know about other issues in the code.
-- From time to time the analysis becomes divergent, and what we analyze on a per patch basis may differ a little bit than what we actually have on the latest snapshot that is created on the entire code base.

I will apply the same reasoning for the Coverity analyzer like we do for `clang-tidy` and thus we will eliminate this inconvenient.
Jonathan thank you for the feedback, right now we are relying solely on what Coverity server is providing us, and it seems it fails from time to time. There are several issues why this might happen:
- The codebase that the patch is used is newer than the last snapshot captured by the coverity server and hence it doesn't know about other issues in the code.
- From time to time the analysis becomes divergent, and what we analyze on a per patch basis may differ a little bit than what we actually have on the latest snapshot that is created on the entire code base.

I will apply the same reasoning for the Coverity analyzer like we do for `clang-tidy` and thus we will eliminate this inconvenient.

Back to Bug 1542163 Comment 4