[Adium-devl] Static analysis in buildbot

Jeffrey Melloy jmelloy at gmail.com
Mon Jul 7 23:12:21 UTC 2008


It seems like you could fairly easily make it a two-step process.  After the
build runs once, a list is compiled of each individual function, etc and
stored in a CSV.  The next time, it builds the same list and then compares
against the CSV.  The delta gets added to Trac, and the new results go into
the CSV with the revision they occured.

Jeff

On Mon, Jul 7, 2008 at 3:37 PM, David Smith <catfish.man at gmail.com> wrote:

>
> On Jul 7, 2008, at 3:32 PM, Ryan Govostes wrote:
>
> >
> > On Jul 7, 2008, at 5:20 PM, Christopher Forsythe wrote:
> >
> >> There's an xml-rpc api that should provide a way to submit tickets
> >> to the trac ticket.
> >
> > That's true, though this isn't the biggest hurdle.
> >
> > More importantly, how do we identify identical problems across builds?
> > Can we automatically detect when a problem stops, or update tickets
> > when a file is changed but the problem remains?
> >
> > -- Ryan
>
> People interested in this subject should check out the clang mailing
> list archives, and probably sign up for said ML.
> http://lists.cs.uiuc.edu/pipermail/cfe-dev/2008-July/thread.html
>
> in particular,
> http://lists.cs.uiuc.edu/pipermail/cfe-dev/2008-July/002167.html
>  and followups
>
>                        David
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20080707/41705db9/attachment-0001.html>


More information about the devel mailing list