Artifacts Associated With Ticket 248a4966e8d02688443d40b2e716ec73e9419c8d
Ticket change [15bb2ceb7c] (rid 4705) by matt on 2013-07-21 22:41:43:
- comment initialized to:
<verbatim> 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 </verbatim>
- foundin initialized to: "v1.5508"
- severity initialized to: "Important"
- status initialized to: "Open"
- title initialized to:
somehow bad testdat.db got created. need way to recover and if possible prevent
- type initialized to: "Code_Defect"
- comment initialized to:
Ticket change [5f0b9a1dab] (rid 5270) by matt on 2013-09-11 23:08:08:
- icomment:
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.
- login: "matt"
- mimetype: "text/x-fossil-plain"
- priority changed to: "Immediate"
- resolution changed to: "Fixed"
- status changed to: "Closed"
- icomment: