Hi Bernd, > Well except from that it is basically just a file and not a database > where we keep track of what valgrind already found in previous runs and > for which errors tasks have already been submitted you are right there > is additional storage involved. With each valgrind run that file gets > updated. If an error already contained there would be found by valgrind > no new entry would be generated in that file. Only new things get a new > entry with a new Valgrind ID there. We than have a program submitting > issuzilla tasks for new issues contained in this file after a valgrind > run and which in turn updates state information in that file by looking > at the already submitted issuezilla tasks. As later on eventually > issuezilla tasks may be set to duplicate it´s quite possible that two > generated Valgrind ID´s might be fixed with one issuezilla task (when > you resolve the issuezilla issues to the last one in the list formed by > set duplicate-to fields of issues).
Thanks for the explanations. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
