|
2013-09-11
| ||
| 23:08 | • Closed ticket [248a4966e8]: somehow bad testdat.db got created. need way to recover and if possible prevent plus 5 other changes artifact: 5f0b9a1dab user: matt | |
|
2013-07-21
| ||
| 22:41 | • New ticket [248a4966e8]. artifact: 15bb2ceb7c user: matt | |
| Ticket Hash: | 248a4966e8d02688443d40b2e716ec73e9419c8d | |||
| Title: | somehow bad testdat.db got created. need way to recover and if possible prevent | |||
| Status: | Closed | Type: | Code_Defect | |
| Severity: | Important | Priority: | Immediate | |
| Subsystem: | Resolution: | Fixed | ||
| Last Modified: | 2013-09-11 23:08:08 | |||
| Version Found In: | v1.5508 | |||
| Description: | ||||
ERROR: problem accessing test db /mfs/matt/data/megatest/tests/installall/links/stdrel/ww29.7/eggs/trace, you probably should clean and re-run this testno such table: test_data Error: (prepare) no such table: test_data #<sqlite3:database> "SELECT id,test_id,category,variable,value,expected,tol,units,comment,status,type FROM test_data WHERE test_id=? AND category LIKE ? ORDER BY category,variable;" Call history: db.scm:256: g527 db.scm:268: sqlite3#set-busy-handler! db.scm:275: debug:print-info common_records.scm:60: debug:debug-mode db.scm:277: call-with-current-continuation db.scm:277: with-exception-handler db.scm:277: ##sys#call-with-values db.scm:285: sqlite3#execute db.scm:277: k537 db.scm:277: g541 db.scm:281: condition-property-accessor db.scm:280: g545 db.scm:280: debug:print common_records.scm:51: debug:debug-mode common_records.scm:52: with-output-to-port db.scm:1876: sqlite3#for-each-row | ||||
| User Comments: | ||||
matt added on 2013-09-12 05:08:08:
v1.55 has several defenses in place to prevent this. It is now very rare. It can still happen but the full resolution requires a change in the architecture of testdat.db location and access. I'm calling this fixed for now. | ||||