https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8033
--- Comment #2 from Sidney Markowitz <sid...@sidney.com> --- (In reply to Kevin A. McGrail from comment #1) > Interesting. Can you work with the tester to get the output files > referenced Difficult communicating with the tester. I tried that with this specific tester once before with never a reply. I have been uploading test builds with diagnostic output going to STDERR so it shows up in the test reports. Each time I do takes about 24 hours before that particular test machine gets to it and I can see the results. Makes me nostalgic for my first programming days submitting punch card decks for an overnight run on the mainframe. At least this time I can run on my machine to get immediate feedback on typos before I submit it :) I have it narrowed down to the second call to salearnrun getting that first die error and the sqlite db file being deleted sometime during that call. Sometime tomorrow I should find out what can be found by adding -D learn,sa-learn,bayes to that one call to sa-learn that is dying. There would be more output than I want if I tried blasting out a -D all, given that this test will be run by hundreds of test machines other than just the one or two that get the error, so I'm trying just those three -D channels first. At least it isn't a Heisenbug - The error is consistent on the couple of machines on which it happens. -- You are receiving this mail because: You are the assignee for the bug.
