[Cdash] ITK test showing up on Slicer3 dashboard

Bill Lorensen bill.lorensen at gmail.com
Sun Jan 11 13:35:09 UTC 2009


It really does not happen all that often. Probably not worth the
effort right now.


On Sun, Jan 11, 2009 at 6:23 AM, Julien Jomier
<julien.jomier at kitware.com> wrote:
> I think the problem comes from the non-transactional nature of the MyISAM
> storage engine that we use. When adding a new test we get the resulting
> testid from the database, which might be different if another test was added
> in the meantime, which happens a lot with concurrent submissions, especially
> at night.
> The best way to fix this is to switch to using InnoDB as the storage engine,
> however this would require some work to do the translation (but it's
> doable). InnoDB should also increase the speed of reading the database (only
> row-locking instead of table-locking).
> Julien
> Bill Lorensen wrote:
>> This remains a recurring problem...
>> This time, the ITK test shows up on the Slicer3 dashboard.
>> http://www.cdash.org/CDash/testDetails.php?test=6271386&build=247911
>> Bill
>> _______________________________________________
>> Cdash mailing list
>> Cdash at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/cdash

More information about the CDash mailing list