View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0015452 | CDash | (No Category) | public | 2015-03-17 09:49 | 2015-03-17 10:12 | ||||||||
Reporter | Clinton Stimpson | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0015452: some cdash logs not clearing | ||||||||||||
Description | There are some errorlog entries not associated with a buildid. These apparently don't get cleaned up, and I don't see a way to clean them. If I run this sql statement: select * from errorlog where buildid=0; I get a result of 34497 rows. Most of them contain "(ctest_parse): error: could not create handler based on xml content" And some contain "(ctest_parse): Checksum failure on file: ...." Looking at the php source, only those associated with buildids can be cleaned up. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Relationships | |
Relationships |
Notes | |
(0038228) Clinton Stimpson (reporter) 2015-03-17 10:12 |
I manually deleted most of the rows in the errorlog table, and now I can see the errors show up in the browser, with a button allowing me to delete them. So it appears to work fine except that if there is a very large number of rows, it doesn't work. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-03-17 09:49 | Clinton Stimpson | New Issue | |
2015-03-17 10:12 | Clinton Stimpson | Note Added: 0038228 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |