Log analysis code
Joe Marcus Clarke
marcus at marcuscom.com
Wed Oct 19 18:19:42 EDT 2005
On Thu, 2005-10-20 at 00:16 +0200, Oliver Lehmann wrote:
> Joe Marcus Clarke wrote:
>
> > My plan is to write code into the web frontend (frontends in 2.x) to
> > display this failure reason tags, and allow people to click on the tag
> > to get the description. While I have no problem writing the code
> > myself, I was wondering if a more creative soul (oliver, pav, I'm
> > looking at you) would be willing to do it?
>
> How does the reason gets determined? is it stored in the DB or does it
> needs to be detected everytime again by running those patterns through
> the logfile? If it's been stored in the db (what i would favorise to
> reduce file-i/o and doing the same thing many times) I don't think it
> will be hard to add to www(-exp) and I can do this even if I'd been busy
> latly ;)
The reason is stored in the database in the build_ports table. Check
out the schema changes that went into HEAD. The log is only analyzed
once per port build.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://marcuscom.com/pipermail/tinderbox-list/attachments/20051019/141738a2/attachment.bin
More information about the tinderbox-list
mailing list