| Subject: | Fails often when a previous run left a broken DB file behind |
As per subject: fails often when a previous run left a broken DB file behind;
But also: fails often when run in parallel.
It seems that two smoker processes downloading the mirror database at the same time can disturb each other and then leave a broken copy of the DB behind that may or may not be cleaned up automatically. Workaround in the case that the fails are perstistent:
rm -rf ~/.local/share/.perl/ORLite-Mirror
My smoker sent about 35 fail reports between 2014-11-14 and 2014-12-23. The fail reports seemed to indicate that some error message may have been changed in some underlying library or some such, so I did not consider a broken persistent download to be to blame. Sample fail report:
http://www.cpantesters.org/cpan/report/48313497
I'm sorry for the noise, I just did not understand the type of brokenness.
I hope this report helps so far. If my smoker starts to act up again, let me know and I'll probably disable testing of ORLite-Mirror.
Cheers,