[PATCH] D12906: [RFC] Bug identification("issue_hash") change for CmpRuns.py

Honggyu Kim via cfe-commits cfe-commits at lists.llvm.org
Thu Oct 22 06:05:40 PDT 2015

honggyu.kim added a comment.

Hi Anna,

In http://reviews.llvm.org/D12906#272243, @zaks.anna wrote:

> I think you misunderstood my comment. I am not talking about using the existing HTML files here but rather having an HTML viewer, which you could use to browse source code. This viewer would be extended to read the bug reports from the plist files and display them. Currently, we create an html file with source code + report info for each bug report. This does not scale when you have a lot of reports on a single large file (ex: sqlite).

I know you already mentioned about the scalability issue but I was thinking to use the existing implementation since I thought we didn't have the HTML viewer you mentioned as of now. (before I saw Daniel's comment)

> What I describe above is a larger project. What workflow are you trying to support? I think adding the issue hash to the HTML file is fine if you find it to be useful for your workflow...

My workflow is as follows:

1. manage buildbot server to get an event whenever a registered action happened for Linux kernel
2. when an event is received, run clang static analyzer for the current Linux kernel
3. put the each report in the place where anyone can access through web server

Whenever buildbot runs clang static analyzer for Linux kernel and it shows more than 600 bugs. I've received many feedback from my colleagues. They want to see only diff set in HTML format because it has too many bug reports.

That's why I was thinking about connecting plist info to HTML files regardless of using CmpRuns.py or not.


More information about the cfe-commits mailing list